How to check an n8n workflow JSON file
Check exported n8n JSON for malformed nodes, duplicate names and broken connections before importing or handing it off.
Start with a real workflow export
A workflow export is a JSON object containing a nodes array and connections keyed by source node names. A JSON response from an API, an execution log, or a credentials export is a different artifact. Flowprep accepts one workflow object or an array of up to 20 workflow objects. It does not read .n8np packages.
Separate parsing from structure
Valid JSON only means the text can be parsed. A missing node type, duplicate node name, or connection to a nonexistent node can still be present. Run the check and handle structural errors first. A node needs a name, type, positive typeVersion, parameter object and canvas position; exported nodes normally also carry an ID.
Review the connections
Connections refer to names, not the display order of the nodes array. Renaming a node directly in a text editor without updating its connections can leave a broken edge. Flowprep checks the source, target, connection shape and non-negative input index. It preserves non-main connection types, including AI connections.
Finish inside the destination instance
A static check cannot know which community nodes or integration versions are installed in your n8n instance. It also cannot evaluate expressions, test authentication, or predict service responses. Import the workflow, resolve unavailable nodes, reconnect credentials and run a known payload before activating it.
Flowprep keeps the analysis local and the original JSON unchanged.
Open workflow checker →