Short answer
Why Is Zapier Creating Duplicate Records?
Zapier creates duplicate records when the same event reaches more than one active workflow, a retry repeats a non-idempotent create action, or a find-before-create check uses an unstable lookup value. Compare duplicate timestamps and Zap History, identify every workflow that can write the record, then enforce one stable external ID and update an existing match instead of creating again.
Common causes
- Two Zaps or a Zap and a native app automation respond to the same event.
- A webhook sender retries because it did not receive a timely success response.
- An error retry repeats a create action that completed remotely but did not return cleanly.
- The search step uses a mutable or non-unique field such as name, status, or formatted phone number.
- A loop, path, or line-item mapping creates once per item unintentionally.
Diagnostic steps
- Capture the IDs, creation times, and field differences for two duplicate records.
- Match each timestamp to Zap History and inspect the Zap, version, and input payload.
- List all Zapier, Make, app-native, and custom workflows with write access to the destination.
- Choose an immutable source ID and store it in a dedicated destination field.
- Search by that ID before creation; update when found and create only when absent.
- Test retries and simultaneous events, then monitor the destination after publishing.
Example
A CRM lead arrives through both a form’s native CRM integration and a Zap. The records appear seconds apart with different owner fields. Disabling one writer and using the form submission ID as a unique external key prevents the second create.
Caveats
A search-then-create design can still race when two runs execute simultaneously. For high-volume or consequential workflows, use a destination-side unique constraint, serialized queue, or idempotency support. Merge or delete production duplicates only after confirming downstream references and audit requirements.