Webhook-triggered workflows that appear to perform writes without an obvious dedupe/idempotency signal.
Scan an n8n workflow for reliability risk signals.
Drop in an exported workflow JSON and get an immediate heuristic pass for duplicate-action risk, retries, silent failure patterns, webhook handling, test endpoints, embedded secret signals and handoff clarity. The file stays in your browser.
The file is parsed locally in your browser. This scanner does not upload the workflow or credentials to a server.
Use the scanner as a first pass, not a release certificate.
The most expensive failures often depend on business context: which writes are irreversible, what partial success means, whether an upstream system retries, and how the workflow should recover. That requires workflow-specific review, production monitoring or regression cases.
Mutating HTTP calls without explicit retry handling and workflows that continue after failed writes.
Missing explicit webhook auth and immediate acknowledgement before downstream work finishes.
External-call workflows without an obvious Error Trigger/errorWorkflow configuration.
HTTP nodes containing common sandbox, staging, localhost or test endpoint signals.
Credential-like literals in code nodes, disabled nodes and generic node names that weaken handoff clarity.