n8n Workflow Checker: Free n8n Workflow Auditor

An n8n workflow checker scans your exported workflow JSON for problems before they break production. Sophrai’s free auditor flags nodes removed in n8n 3.0, hardcoded API keys, webhooks without authentication, orphan and disabled nodes, risky Code nodes, leftover pinned data and a missing error workflow, all inside your browser.

Privacy: the check runs 100% in your browser. Your workflow JSON is never uploaded, stored or logged, and any secret it finds is masked in the report.

How to check an n8n workflow

  1. In n8n, open the workflow, click the ⋯ menu and choose Download. You can also select all nodes and copy them (Ctrl+C or ⌘+C).
  2. Paste the JSON into the box above, or drop the .json file onto it.
  3. Click Audit workflow. You get a health score from 0 to 100 and a list of findings sorted by severity.
  4. Fix the critical and high findings first. Each one names the node, explains why it matters and tells you how to fix it.
  5. Click Copy Markdown or Download .md to paste the report into a ticket, a client handover or your Git repo.

What the auditor checks

CheckWhat it findsTypical severity
n8n 3.0 compatibilityNodes and helpers that n8n 3.0 removes: Function, Function Item, Item Lists, Cron, Interval, legacy OpenAI, AI Agent v1 modes, Edit Image v1, $getPairedItem and moreCritical
Hardcoded secretsOpenAI, Anthropic, Stripe, GitHub, Slack, AWS, Google, Telegram and other keys, Bearer tokens, passwords in URLs and literal auth headersCritical
Webhook securityWebhook nodes with no authentication, public chats without a loginHigh
Code nodeseval(), new Function(), shell commands, process.env, infinite loops, very long codeHigh to low
Error handlingNo error workflow set in workflow settingsMedium
StructureOrphan, unreachable and disabled nodes, connections to missing nodesMedium to low
Pinned dataTest data left pinned in the export (often real customer data)Medium

The n8n 3.0 rules come only from n8n’s official v3.0 breaking changes page, and every finding links to its source. For the full list of changes, read our guide to n8n 3.0 breaking changes. Before upgrading, also open Settings → Migration Report on your own instance: it is the authoritative check for your setup.

Want to know what your workflows cost to run? Try the n8n Cost & Hosting Planner.

FAQ

Is my workflow JSON uploaded anywhere?

No. The n8n workflow checker runs entirely in your browser with JavaScript. Nothing is sent to Sophrai or any other server, and secrets in the report are masked.

Will this tell me if my workflow works in n8n 3.0?

It flags every node, node version and helper that n8n’s official breaking changes page says is removed or changed in 3.0. It is a static check of the JSON, so also run the Migration Report in your n8n instance and test on a separate instance before upgrading.

What should I do if it finds a hardcoded API key?

Treat the key as leaked: revoke or rotate it with the provider first. Then store the new key in an n8n credential, such as Header Auth, or reference it with an expression like {{ $env.MY_KEY }} so it never sits in node parameters.

Why does a missing error workflow matter?

Without one, a failed production run only shows up if someone opens the executions list. An error workflow that starts with the Error Trigger node can alert you in Slack, email or Telegram the moment something fails.

Does it work with workflows from the n8n template library?

Yes. Paste any exported or copied workflow. Templates are worth checking: a community scan found that about 17% of public n8n templates use at least one node that n8n 3.0 removes or changes.

How is the health score calculated?

Every workflow starts at 100. Each finding subtracts points by severity: 25 for critical, 12 for high, 6 for medium and 2 for low. Any critical finding caps the score at 59.