What is an n8n workflow JSON file?

An n8n workflow JSON file is the exported representation of an n8n automation workflow. It contains all nodes, their configurations, connections between nodes, credentials references, and workflow settings in JSON format. You can export any workflow from n8n by clicking Download in the workflow editor, and import workflows by pasting or uploading the JSON file.

Why is my n8n workflow JSON invalid?

Common reasons an n8n workflow JSON is invalid include: malformed JSON syntax (missing commas, brackets, or quotes), missing required fields like nodes array or connections object, nodes with duplicate names, connections referencing node names that don't exist, missing node type fields, or corrupted JSON from copy-paste errors. This validator checks for all of these issues and explains exactly what needs to be fixed.

n8n Workflow JSON Validator Online Free — Validate & Debug n8n Workflows

n8n Workflow JSON Validator — Fix Workflow Errors Instantly

n8n is one of the most popular open-source workflow automation platforms, used by developers, marketers, and automation engineers to build complex multi-step workflows connecting APIs, databases, and services. Every n8n workflow is stored as a JSON file — and when that JSON has errors, the workflow silently fails or refuses to import.

This free validator performs a deep structural analysis of your n8n workflow JSON: it checks for valid JSON syntax, verifies the presence of required top-level fields (nodes, connections), validates every node's required properties (id, name, type, position), detects broken connections referencing non-existent nodes, finds duplicate node names that cause routing conflicts, and assigns a health score so you know exactly how production-ready your workflow is.

🔴

Most Common n8n Workflow JSON Errors

These are the errors this validator catches most frequently:

Invalid JSON syntax — missing comma, bracket, or quote from manual edits
Missing nodes array — the workflow has no node definitions
Missing connections object — nodes exist but nothing connects them
Node missing type field — n8n can't identify which node module to load
Node missing id or name — causes silent routing failures
Broken connection reference — a connection points to a node name that doesn't exist
Duplicate node names — two nodes with the same name cause connection conflicts
Missing position — node won't render in the visual editor

✅

What a Valid n8n Workflow JSON Contains

A properly structured n8n workflow JSON has these components:

name — workflow display name (string)
nodes — array of node objects, each with id, name, type, typeVersion, position, parameters
connections — object mapping source node names to target connections
active — boolean, whether the workflow is currently active
settings — workflow execution settings object
id — unique workflow identifier (auto-generated by n8n)
tags — optional array for workflow organization

🔧

How to Fix n8n Workflow JSON Errors

After identifying errors with this validator, here's how to fix the most common ones:

JSON syntax error — use a JSON formatter (like this tool's Format button) to identify the exact line and character causing the error
Missing required field — add the field manually in a text editor or recreate the node in n8n and re-export
Broken connection — update the connection object's key to match the exact node name, including case
Duplicate names — rename one of the duplicate nodes in n8n editor before re-exporting
Missing node id — generate a UUID (e.g. using our UUID generator) and add it as the id field

📦

Sharing & Importing n8n Workflows

n8n workflows are frequently shared in JSON format on community forums, GitHub, and template marketplaces. Before importing a shared workflow:

Always validate first — shared workflows may have been edited manually or exported from a different n8n version
Check credential references — nodes with credentials fields will need you to map them to your own credential IDs
Review node versions — older workflows may use deprecated node types that have been renamed in newer n8n versions
Check for webhook URLs — any HTTP trigger nodes will generate new webhook URLs after import
Test in staging first — run the imported workflow with test data before activating on production

Frequently Asked Questions — n8n Workflow JSON

Why does my n8n workflow fail to import? +

The most common reason an n8n workflow fails to import is invalid JSON structure. This typically happens when the JSON was manually edited and a comma, bracket, or quote was accidentally added or removed. Other causes include: the JSON being from a significantly older or newer version of n8n with incompatible node structures, missing required top-level fields like nodes or connections, or the file being corrupted during download. Use this validator to pinpoint the exact issue before attempting to fix it.

What does "connection references unknown node" mean in n8n? +

This error means the connections object in your workflow JSON references a node by a name that doesn't exist in the nodes array. n8n uses node names (not IDs) as keys in the connections object. If you rename a node in the editor, the connections object should update automatically — but if you manually edited the JSON, the connection key may no longer match the node's current name. Fix it by ensuring every key in the connections object exactly matches a node name in the nodes array, including capitalization and spacing.

How do I export an n8n workflow as JSON? +

To export an n8n workflow as JSON: open the workflow in the n8n editor, click the three-dot menu (⋮) in the top-right corner of the editor, and select Download. This downloads a .json file containing the complete workflow definition. You can also use the n8n REST API endpoint GET /workflows/{id} to programmatically export workflows. The exported JSON can be shared, imported into another n8n instance, stored in version control, or validated with this tool.

Can I manually edit n8n workflow JSON files? +

Yes, you can manually edit n8n workflow JSON files in any text editor, but it requires care. The most common mistakes are JSON syntax errors (missing commas between objects, unclosed brackets, trailing commas) and mismatched node names in the connections object. It's best to use a code editor with JSON syntax highlighting like VS Code, which will catch syntax errors before you try to import. After editing, always validate the JSON with this tool before importing back into n8n. For complex changes like adding new nodes, it's safer to make the changes in the n8n visual editor and re-export.

What is the n8n workflow health score? +

The workflow health score is a composite metric calculated by this validator based on: JSON validity (40 points), presence of all required fields (20 points), valid node configurations (20 points), clean connection structure (10 points), and best practice recommendations (10 points). A score of 90–100 means the workflow is production-ready. 70–89 has minor warnings but should work. Below 70 indicates structural issues that may prevent the workflow from running correctly. This score helps you quickly assess the quality of a shared workflow before importing it.

n8n Workflow JSON Validator