Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Zapier keeps creating duplicate records

Short answer

Duplicates usually come from a replay of a full run, a webhook that sends several events, a trigger that picks up the same record again, or a Zap with no check for an existing record. Find which one applies before deleting anything, then add a lookup step.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The same customer appears two or three times in my CRM.
  • Invoices or orders were created twice.
  • Zap history shows two runs for one event.
  • The duplicates started after an outage or a replay.
  • Two Zaps seem to do the same job.

Why does this happen?

  1. A replayed run repeats actions

    Replaying an entire run replays every step, including the trigger, using the original trigger data, and shows as a separate run. Steps that already succeeded can create their record a second time.

  2. One webhook request can hold many events

    With Webhooks by Zapier, an array of JSON objects in one request runs the Zap once per object. If the sending system also resends the request, each object runs again.

  3. The destination has no duplicate check

    A Create action simply creates. Without a Find step or a unique key, a second run produces a second record.

  4. Two Zaps or two triggers cover the same event

    An old Zap, a copy made for testing or a second workflow in the destination app can all react to one event.

What can I do about it today?

  1. Do not mass-delete yetSome copies carry newer details. Mark duplicates first and decide later.
  2. Compare timestampsCheck whether duplicates arrive seconds apart (double trigger) or after an outage (replay).
  3. List every Zap that touches the appLook for an old or copied Zap doing the same job and turn off the extra one after asking its owner.
  4. Pause new runs only if harm is ongoingIf invoices are being duplicated and sent, turn that one Zap off and tell the team.
  5. Keep an export of the dataDownload the list before cleaning, so a mistake can be reversed.

When should I bring someone in?

  • The duplicates involve invoices, payments or sent customer emails.
  • The numbers are large and a manual cleanup would take days.
  • You cannot tell which copy is correct.

How do I handle it?

  1. Trace one duplicateI follow a single duplicate back through history to the run, the trigger and the data that created it.
  2. Choose a keyA reliable identifier, such as an order number or email address, decides what counts as the same record.
  3. Check before createThe flow looks up the key first and updates instead of creating when it finds a match.
  4. Clean up carefullyI merge or archive duplicates from an export, never by bulk delete, and keep the original file.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is it a Zapier bug?

Usually not. The common causes are replays, repeated webhook requests and a missing duplicate check, and each can be traced in history.

Can the duplicates be merged automatically?

It depends on the destination app and on how reliable the key is. I would test on a copy first.

Will a replay always duplicate?

Not always, but Zapier states an entire-run replay repeats every step, so steps that create records are at risk.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.