Will your n8n flow
do it twice?
A duplicate webhook. A timeout after a successful write. One accidental retry can send two emails, create two leads, or trigger two payments. Scan an exported workflow for potential retry and duplicate-operation risks before they ship.
01. Scan your workflow
Export a workflow as JSON in n8n. Choose it below. The file is read only in this browser tab. Nothing is sent to our server.
The scanner reads node types, connection structure and safety-related settings. It does not run your automation or inspect live credentials.
What it looks for
Could retries create the same email, CRM contact or API write twice?
Does an action repeat even after the remote system may have succeeded?
Are errors ignored or routed to a review/recovery path?
This is a static heuristic review, not a security certification or proof that every duplicate is prevented. Manual review is essential for high-impact workflows.
From possible risk to a tested boundary.
A scoped $49 human-reviewed Automation & QA Diagnostic, with findings and prioritized next actions. The free tool and the paid service are separate; there is no automatic remediation.
Reserve a stable event ID
Use the webhook provider's event ID, a business key, or a durable unique constraint. Do not trust the HTTP request arriving only once.
Check before replay
A timeout can mean "unknown." Check the remote write before retrying. A non-atomic check-then-write can race under concurrent events.
Test the failure path
Send the same event twice, then simulate a timeout after the downstream write. Verify only one irreversible effect occurs.