3/29/2024 0 Comments Airtable record zapierI think you’re correct, this is not entirely Airtable’s fault. Significant changes fire off a POST to a Zapier webhook, which in turns updates Airtable accordingly. In the end, I got around the problem by ignoring Zapier’s triggers instead, I wrote a simple Google Apps Script that’s triggered by a edit to any cell in the sheet.Admittedly, if it is a problem with Zapier’s architecture, I can’t imagine what purpose it must originally have served, nor can I fathom why it wasn’t fixed years ago. In any case, this is essentially the same limitation everyone complains about with Zapier’s Airtable triggers – but having nothing to do with Airtable. Given this was an advertising buy-scheduling system, it seemed quite likely for an ad campaign to be shifted off and then back on to a given date, rendering it invisible to Zapier.¹ For instance, I recently used Zapier to link Google Sheets to Airtable for a client, and I quickly ran into the middleware’s refusal to trigger on a cell update if it meant the cell was returned to a value Zapier knew it to have previously held. If you look into many Zapier integrations, you’ll find this to be a frequently recurring limitation for a wide range of apps. I’m not certain the problem is with Airtable. Now if you update it again and check that box, it will re-trigger the workflow again in zapier. Then at the end of the workflow, I go back and use the ID i got in the first step, and update that row to uncheck the ‘Ready for Update’. Then, in zapier, you can perform a lookup for everytime a row is added to this view. Then, as Roman suggested, create a view that is filtered to only show rows who have this ‘Ready for Update’ checked. By having a field that you have to check to notify its ready for updating, you avoid that issue. I think one of the concerns with update triggers is when to perform them, what if you updated one cell, then in the process of updating the next cell and your process triggers due to the first update. I’ll do a full blog post later explaining what I did, but basically set up a checkbox field that I labeled ‘Ready for Update’. Integromat - but note that Integromat has at least 2 important Airtable limitations that you need to be aware of, as I describe in this thread.So I got curious and based on others approaches was able to pretty easily implement this in zapier. Yes, it’s true that neither of these workarounds will immediately trigger an action when something in Airtable happens.īut they trigger frequently enough that these workarounds could potentially be used in a variety of different real-world scenarios.įor true instant automatic triggering, we can use: So both of these solutions are “workarounds” instead of “solutions”, because they are essentially scheduling your Airtable actions to happen on a regular interval. Schedule by Zapier can only run a maximum of once every 60 minutes. We can use the Schedule by Zapier module as our trigger for any Airtable action as well. You don’t even need to know any JavaScript - you just set Zapier to run this simple JavaScript code that always returns “true”:Īnd that’s it! Based on which paid Zapier plan you’re on, this trigger will automatically trigger every 15 minutes, every 2 minutes, or every 1 minute. (Meaning that these workarounds are not really “full solutions”, but they should be acceptable for a wide variety of use cases.)īoth of these workarounds require a paid Zapier plan:Īs described in this Airtable blog entry, we can use Zapier’s Code by Zapier module as the trigger for any Airtable action (such as searching records to give us the records we’re looking for). In regards to Zapier not being able to trigger multiple times for the same record, I have discovered 2 relatively acceptable workarounds to this issue. The problem with “New Record in View” is that it will only trigger once for the entire lifetime of the record (in that view).īut I have discovered some pretty cool workarounds! One of the big limitations for Airtable users who are trying to use Zapier is that we only have 2 triggers: “New Record” and “New Record In View”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |