8h • Chat 💬
⚙️ Make.com Tip
The webhook bug that silently duplicates your automations (and how to kill it)
The problem:
Webhooks retry. If Stripe, Typeform, or your CRM doesn't get a fast
enough response from Make, it resends the same event — sometimes minutes
later. If your scenario isn't built to notice, you get duplicate orders
processed, duplicate emails sent, duplicate rows created. This is one of
the most common "why did this run twice?!" issues in Make.
The fix (step by step):
1. Add a Data Store at the very start of your scenario (Make has this
built in — no external database needed)
2. Right after your webhook trigger, add a "Search Records" step that
checks the Data Store for the event's unique ID (order ID, submission
ID, whatever the source provides)
3. Add a Router: if the ID already exists in the Data Store → stop the
scenario here (use a Filter set to only continue if NOT found)
4. If it's new, add an "Add/Replace Record" step to save that ID to the
Data Store, then let the rest of your scenario run as normal
Why this works better:
Most people try to solve duplicates with "just make the scenario faster"
— but that doesn't fix the root cause. The Data Store check makes your
scenario idempotent: no matter how many times the same event fires, it
only actually processes once. This is the same pattern real engineering
teams use, just built with modules instead of code.
🔧 Try it: Pick your webhook-triggered scenario that matters most (order
processing, lead capture, form submissions) and add this check first —
it takes about 10 minutes to set up.
💬 Has a duplicate webhook ever caused you a real headache? What happened?
1
0 comments
⚙️ Make.com Tip
powered by
skool.com/futureminds-ai-2442
Build AI automations, AI agents with Make.com and Voiceflow. Learn practical skills that save time and make money.
Suggested communities
Powered by