I created a Zap that finds duplicates in Zapier tables after new records are added and then (intended to) update a field with “duplicate” once duplicates are found. Everything is seemingly connected/working...but as the Zap runs it ONLY updates the “new” record and not the “old” record in Zapier tables that it has also found as a duplicate.
How do I get the Zap to update BOTH of the duplicative records that were returned with record locators?
Pictures below for key steps/activities:
Make sure you test live with the Zap turned ON, then review your Zap Runs history details to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/
Help links for using Looping: https://zapier.com/apps/looping/integrations#help
Great advice - for some reason the Zap isn’t triggering when I check the run history (which is why it works during the build/test but not with real data). It seems to be set up correctly:
(And when I click on “Open in Tables” it opens the correct Table….and tests go through). It DOES work/trigger when I manually add a row with the data (so it doesn’t seem to be my Zap set up). But it does NOT work when I import data into the Zapier Table. Is there a known bug with importing data that is supposed to trigger “new or updated records” zaps? Or what is the trigger set for importing data if it isn’t new or updated records?
Importing data will not trigger Zaps to run that are connected to the Zapier Table.
This is likely to prevent hitting throttling limits in Zaps, since the data import could have 1,000s of records.
The workaround is to configure the Zapier Table with a “control” field (e.g. checkbox, etc.) that you can use to configure as the field to watch for updates in the Zap trigger for updated record.
That way, after you import the data, you can manually update the records to adjust that field, which will then trigger the associated Zap to run.
NOTE: These are the settings in Zapier Table that reference “manually” updating records.
Huge bummer that Zapier Tables only considers “new records” to be manually created records vs imported records, as I am not sure what business would trying to use automation and is interested in adding records to the table manually or wants to “check a box” next to all of the records they just imported (either manually or using more of their Zap tasks before tasks to do the actual work).
As an example, if a user imports 10k records and the user is not aware the Zapier Table is connected to Zaps that might trigger a ton of Zap Runs.
Then that use case could do more harm and good, so better to be safe than sorry when designing features to put purposeful friction in places where bulk actions can happen.
Plus, apps generally have API limits.
So if the data import triggered 10k records, then that likely will cause the Zap Runs to encounter errors.
That leads to creating new problems to deal with and solve.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.