Same webhook arrives twice, customer gets duplicate email
Source may retry. Make the flow idempotent with a unique-key check before processing.
support/workflow-automatisering/idempotency-flow-designsteps: 4
Try this first
- Identify unique ID in payload (event_id, order_id)
- Store processed IDs in a table or cache
- Skip if ID already seen, log the skip
- Cache TTL long enough for retry windows
When to bring us in
On financial duplicates: rollback and manual reconciliation.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.