Another option might be to pass the record IDs of the records to process as part of the webhook call. With a button-click as the kickoff point, I might do something similar: first have the script mark all of the records I want to process so that they appear in a specific view, then kick off the webhook call to Integromat, where it would grab all records from that view and un-mark them as it went. :slightly_smiling_face: If I’m tying into other services via Zapier or Integromat (which I hardly ever do any more), my old go-to process was to build a view to isolate the records I wanted to process, then have Integromat collect all records from that view at the start of a scenario. If I’m just updating a batch of records and it’s something that I can accomplish directly in Airtable using either a Scripting block or an automation that runs a script action, I tend to lean in that direction. Adding support for those to the example above, it could look like this: let url = '' Īwait fetch(url + config.recordID + '&companyName=' + encodeURI(panyName) + '&companyEmail=' + encodeURI(panyEmail)) Also, the argument values must be URL-encoded, which can be done in the script with the encodeURI function (or, alternately, adding formula fields to your base to encode the data using Airtable’s ENCODE_URL_COMPONENT() function).įor example, say that I added two more input variables named companyName and companyEmail to the input variables section. All arguments after that must be prefaced by an ampersand (&). As you see in my example above, the first argument must be prefaced by a question mark (?). To add those to the URL, append them one at a time after the root URL. Our plan is to schedule this to happen every night at 7PM so that it will be consistent and won't require us to run it by hand.Welcome to the community, :grinning_face_with_big_eyes: Adding more input variables to the script is done via the built-in system on the left side of the script editor. My feeling is that we might need two exclusive Zaps, one for singe records and another for grouping. Group records that share an email field and create a grid format.This way we're not sending 8 nightly reminders when we could just be sending one but this is all based on some logic that I'm having trouble building in Zapier.

When there are multiple records with the same email (meaning multiple gigs in one day) we want those to be grouped together like a digest and look like so.

We want those records emailed out to the email listed. The record looks like this- DATE | TIME | CONTRACTOR EMAIL | CHECKBOX | COMMENTS

If the date in a record is tomorrow AND there is a box checked it will enter this view. We have a view in Airtable currently set up for the following: Since then it doesn't work the way we need so we've rolled it back and are now trying to build a better solution. This is something many of our folks really want and we had it set for a while with Airtable automations. The function is to email contractors at our agency to remind them they are working the next day. Hoping you can help me as I'm new to Zapier and the ai build is also not making the most sense to me. We've been missing out on this one function lately because the automation is just lacking for us.

Airtable send all records to zapier