Thanks, this is helpful. I’m planning to do exactly what you mentioned in the video. I have a table in Airtable that currently maps Zoom meeting types to the number that the Zoom API expects. I actually don’t want that table so I plan to move this info into Make using variables. Great stuff. I appreciate your videos.
I havent said "OHHHH!" that often to a RUclips video in a long time. THANK YOU. Here I was thinking variables were only an org-wide data storage mechanism in Make! 😅
@@XRayAutomation that was incredibly timely. I went back and rewrote the automation I'd been struggling with and it works great. Where I need this the most often is find-or-create - I need to find an existing resource and use its ID, OR if it doesn't exist, create a new one and use its ID in a later stage. The scenario-local variable is the piece I was missing for stuffing the found-or-created ID somewhere so that the next phase can use it.
Thanks, this is helpful. I’m planning to do exactly what you mentioned in the video. I have a table in Airtable that currently maps Zoom meeting types to the number that the Zoom API expects. I actually don’t want that table so I plan to move this info into Make using variables. Great stuff. I appreciate your videos.
Glad it was helpful!
I havent said "OHHHH!" that often to a RUclips video in a long time. THANK YOU. Here I was thinking variables were only an org-wide data storage mechanism in Make! 😅
Aww, thanks! I’m pumped that you got that “OHHHH!” vibe! Variables are way cooler than they sound, right?
@@XRayAutomation that was incredibly timely. I went back and rewrote the automation I'd been struggling with and it works great.
Where I need this the most often is find-or-create - I need to find an existing resource and use its ID, OR if it doesn't exist, create a new one and use its ID in a later stage. The scenario-local variable is the piece I was missing for stuffing the found-or-created ID somewhere so that the next phase can use it.