Hi everyone,
I’m setting up a Zap that sends information from one app to another, but I’m sometimes getting duplicate records when the Zap runs more than once.
What’s the best way to check whether a record already exists before creating a new one? I’d like to avoid duplicates without making the Zap unnecessarily complicated.
Would appreciate any suggestions or best practices for handling this.
+14Hi
Depends on the apps being used in the Zap steps.
Many Zap apps have actions such as Find Record, that have a checkbox to create record if not found, so the step becomes Find/Create record.
Or you can add a Filter/Paths after to then create record if Found = False.
+11Hi
Let us know if you’re still stuck or got it sorted!
On top of Find/Create: duplicates often come from the trigger, not the action. Google Sheets "new or updated row" fires again on every edit, so use "new row" where you can. Normalise the key first (Formatter: lowercase and trim the email) so "A@x.com" and "a@x.com " match. For intake flows, key on the form's submission ID or email, and only continue when Find returns nothing.
Build and deploy automations from AI tools you already use. With Agentic Management, if anything breaks, the agent diagnoses the issue and proposes a fix.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
