Audit an n8n workflow before it fails in production.

Paste the workflow JSON. Ten mechanical checks run in this page — no upload, no account, no server. Every finding names the node and the exact field, so you can check it yourself.

This is the same first pass I run when an agency hands me a workflow that "mostly works". It reads the JSON, not your business rules.

1. Paste the JSON

Nothing leaves the browser: the page is static, the checks are plain JavaScript, and there is no request made after it loads. You can run it with the network disconnected.

What the ten checks are

CheckWhy it costs money
Webhook with no authenticationAnyone with the URL can post into the workflow. This is the most common way a small automation becomes an open door.
Secret written into a nodeThe credential travels inside every export, screenshot and copy of the workflow.
Placeholder left in a live fieldYOUR_API_KEY in a production node means the run fails at the first real call.
Disabled node still wired inThe branch around it runs with data it was never written for.
Expression pointing at a missing node{{ $('Fetch leads') }} resolves to null when that node was renamed or deleted. Silent empty fields, not an error.
No error workflowA failed run leaves nothing but an entry in the executions list that nobody opens.
HTTP call with no retryOne 502 from the other side ends the run and every item behind it.
Writes with no de-duplicationA retry or a repeated trigger writes the same row twice, then someone cleans it up by hand.
More than one triggerTwo entry points on one canvas is how half-finished states appear.
Node connected to nothingIt never runs, so whatever it was meant to do is not happening.

When you want the part a rule cannot see

The mechanical pass finds structure. It cannot tell you that the reminder goes out a day early across a DST change, that a retry double-counts, or that the approval gate lets a stale link publish. That needs the failure cases written down and replayed.

Send me one workflow and I return a written audit of it — the failure cases, not an assurance — free, once, so you can judge the work before paying for anything.

Email one workflow for a free written audit Or see the fixed-price build: $450

Already have a workflow and just want it fixed? $99: you send the JSON, you get the corrected workflow and a 30-minute walkthrough — the file is yours to keep and run, no retainer.

Why trust the report

Because you can disagree with it. Every finding quotes the node and the field, so a wrong one is visible in seconds. The rules are in one readable file and are covered by tests/audit.test.mjs, which fails the build if a rule fires on a workflow that is actually fine.

Known limits, stated up front: it does not execute anything, does not evaluate expressions, and does not know your data. A workflow can pass all ten checks and still be wrong.