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. There are records that I want the same automation to run on multiple times (they change conditions and re-enter the view to trigger that zap more than once), but of course Zapier has no option to turn off the built-in deduplication (also if anybody knows where I can make a formal feature request, please share!).
I was wondering what workarounds others had found for this situation. The current one I use is to use an Airtable automation to feed the record id into a google sheet, and then make a zap that’s triggered by a new row in that google sheet which then finds the record in Airtable and gets whatever other data is needed (or sometimes if the data is sparse or simple text, I put it straight into the google sheet to save needing to go to Airtable).
Obviously this requires using an Airtable automation, as well as extra steps in the zap itself and a helper google sheet. I’ve made single re-run zaps that can be manually triggered in other cases, just by duplicating the relevant zap and view and adding a checkbox trigger to enter the view in AT.
What else have you all used? I know sometimes using an Airtable-native automation is an option, but sometimes it isn’t, and I would love to see how others have gotten creative while staying low or no code.
@Alyssa_B! 👋🏽 Thanks so much for reaching out!
I took a quick peek and can see you’re working with our support team to get this sorted, which is perfect. Definitely keep us posted on your progress!
I’m also super eager to hear what the Community has to share in terms of what’s worked for them! 🤗
Formal feature requests can be submitted via a ticket to Zapier Support to be logged: https://zapier.com/app/get-help
Airtable Automations can be used to trigger a Zap via a Webhook as described here:
This example is a simplified, but could be expanded to pass all the necessary data points to a Zap Webhook - Catch Hook trigger, which would remove the need for an Airtable Find Record step in the Zap.
Another option a la the GSheet workaround you’ve described…
Via an Airtable Automation add a new record to another Table in the Base.
Link to the original Record.
Use Lookup fields to pull over the desired data points.
Then use the Zap trigger: Airtable New Record
Lastly, set up another Airtable Automation to delete these temp records when their Created timestamp = Yesterday.
That will create a self-scrubbing system.