Free Tools /n8n
n8n Workflow JSON Validator
Paste your exported n8n workflow JSON to get a full health score: structural issues, missing error handling, security hygiene, and documentation, not just import errors.
Paste a workflow and click Analyze to see the full report here.
How this tool works
Structural validation first
Confirms your pasted JSON is valid, then checks it has the two required top-level keys any n8n workflow needs: nodes and connections.
Orphan and dangling-reference detection
Flags any node never referenced in connections (excluding triggers), and any connection pointing to a node name that no longer exists, the single most common cause of a broken import after a rename.
Best-practice checks, not just structural ones
Beyond "does it import," checks for missing error handling on external calls, generic unedited node names, hardcoded-looking secrets in parameters, and whether the workflow is documented with sticky notes.
A weighted health score
Every finding is weighted by real-world impact (a dangling connection costs more than a generic node name) and rolled into a single 0-100 score so you can judge workflow quality at a glance, not just read a list.
Frequently asked questions
Does this tool send my workflow anywhere?
No. Validation runs entirely in your browser with client-side JavaScript. Your workflow JSON, which may contain business logic or internal system names, never leaves your device.
Can this tool detect missing credentials?
It flags nodes of types that typically require credentials (HTTP Request, database nodes, most app-specific nodes) when no credential reference is present in the node, but it cannot verify the credential itself is valid or has the right permissions, since that requires connecting to n8n directly.
What does the health score actually measure?
It is a weighted composite: structural issues (broken imports) count most heavily, missing error handling and credential gaps count moderately, and cosmetic issues like generic node names or missing documentation count lightly. A 100 means no findings at all; scores below 60 usually mean the workflow needs real attention before production use.
Why does my workflow show an "orphaned node" that I know is connected?
This usually means the connection references the node by a name that does not match its current name, most often after a node was renamed in the n8n editor without the connections being remapped. Re-saving the workflow in n8n typically fixes this automatically.
Why does it flag a hardcoded secret when I did not put one in?
The heuristic looks for parameter values matching common secret patterns (long alphanumeric strings after words like "key," "token," or "secret," or bearer-token-shaped strings) directly in node parameters rather than as a credential reference. It can produce a false positive on a genuinely random-looking but non-secret value, review the flagged field to confirm.
Can I validate a workflow exported from Make or Zapier?
No, this tool is specific to n8n's JSON schema (nodes array with type/parameters/position, connections keyed by node name). Make and Zapier use entirely different internal formats that are not interchangeable.
More free tools
Cron Expression Builder & Explainer
Turn any cron expression into plain English, or build one from scratch.
n8n Expression Tester
Test {{$json.field}} style expressions against real sample data and see the exact output before pasting into n8n.
Webhook Sample Payload Generator
Generate realistic sample payloads for Stripe, Shopify, HubSpot, and Typeform events, no live trigger needed.