Hope that helps to get you pointed in the right direction. More on how to limit the days a Zap runs can be found here: Use Filters so your Zap only triggers on certain days/times One thing to note here is that if you only want Zap 2 to send out reminders on weekdays you may need to add a Filter by Zapier step to prevent the Zap from running on a weekend. Action: Create Detailed Event (Google Calendar) - set the Repeat Frequency to Daily to make it a recurring event. (Reminder 2).Action: Create Detailed Event (Google Calendar) - set the Repeat Frequency to Daily to make it a recurring event.Here’s a quick breakdown of the Zap triggers and actions you’d need for that sort of workflow: And when you want to stop the reminders you’d just delete the event from the calendar (making sure to tick the option to delete future events too!). Then you can select the description for the event in the Send Email action. Likewise, if you create new empty records (which Airtable may do automatically if you hit the enter key while editing a record), those will trigger your Zap without any additional. So, if you have empty records at the bottom of your table, Zapier will pick those up in testing.
You would add the relevant information from the record into the description for the event. Empty records in Airtable still count as trigger records to Zapier. Then you’d have another Zap that triggers on the event and sends out the reminder. What I’m thinking is that you’d use an app, like Google Calendar for example, in the Zap to create a recurring event. I’d love feedback on whether this helps solve anyone’s issues getting webhook notifications for record creation / updates.įeel free to personally reach out if you need help getting it working - more than happy to help.Thanks for sharing some more details on your requirements here so, in that case I’m wondering if you might be able to handle these reminders using a calendar app. Easily manage your data entry by setting up this automation. I documented the setup in a Medium post: this Pipedream pipeline: for the formatting, the Community site wouldn’t let me include any direct links in this post) It’s similar to the solution some of y’all have described, using Slack as a way to get record updates, but it’s also free.Įnd-to-end, If you add a new record to a base, you’ll get a webhook out with a JSON payload sent to a custom HTTP endpoint for that update: [
I’ve setup webhooks for new records and record updates using a combination of Airtable’s Slack notifications and Pipedream (think Zapier, but optimized for webhooks). I know its not quite automated, but when its something as vital as contact information, it can sometimes be best to have a physical trigger to make sure that things don’t trigger improperly. I am not a coder, and I wanted to pursue this over using Zapier or Make to. But i am trying to figure out how to implement this code to send all the correct fields. Hey all My team uses a Zapier/Airtable combo for a large number of automations, and one thing that perennially bothers me is Zapier’s built-in deduplication for Airtable records. Essentially this is going to be built out in Twilio Studio. You do have to press the button once for each record you update, but it will work every time you press it, and it can repeated any number of times. I am trying to use AirTable to initiate via automation and a script action to make Twilio call and message our clients. It would update the contact information in the first record with Yes in that fields to google contacts, then after it updates it looks back for that same field (using the main ID# we use as a key to identify it) and updates the Yes to “Updated” and puts the timestamp of the button press into another field for records. Air table would then search for any record with “Yes” in the field “Ready for Update?”. The workaround was to set the trigger to be a button push.
That makes it slightly risky to auto sync and update the information as someone could accidentally delete some information and clear it our of our database. We would be constantly adding information to records as we found out people’s cell phone numbers and additional email addresses etc.
So.Send as line items to Google sheets, and then create a new zap with the trigger being new line in Google sheets, which you can send to Airtable. Zapier Automation Platform No-code automation across 6,000+ apps. The best workaround I’ve used for this is to send to a Google Sheet and send those to Airtable. In my office we were wanting to use AirTable to store and centralize contact information and link it to various other records. When a new record is added to a specific view in Airtable, this Zap will send a prompt to Jasper, add the completed prompt to a new document in Google Drive, then add a link to that record to your Ai. So this isn’t a perfect solution, but I do have a manual workaround that actually worked out better for a given use case.