flowprepRuns in your browser
THE FLOWPREP FIELD GUIDE

Find missing node references in n8n JSON

Understand broken workflow edges and missing static expression references, with a practical checklist for n8n exports.

Two kinds of reference can break

The connections object describes visible edges between nodes. Expressions and Code nodes can also refer to another node by name. Fixing a canvas edge does not necessarily repair a named expression, and changing an expression does not reconnect the canvas. Review both when a workflow was edited or copied in pieces.

Check the exported node names

Look for spelling, case, whitespace and renamed nodes. Two nodes with the same name make references ambiguous. Flowprep treats duplicate names and missing connection targets as structural errors. A detached node is a review item because it may simply be an unfinished branch.

Understand static expression checks

Flowprep looks for literal names in the common $("Node name") and $node["Node name"] forms inside expression fields and Code nodes. A missing match is marked for review. Computed names, escaped names and arbitrary code are outside this check; a matching name also does not establish that data exists at execution time.

Repair in n8n and re-export

Use the destination editor to reconnect or rename nodes, then inspect expressions that use those nodes. Run with a payload that reaches the affected branch. Export the repaired workflow and check that copy so the file you hand off matches the tested canvas.

Check the file you will actually hand off.

Flowprep keeps the analysis local and the original JSON unchanged.

Open workflow checker →

Official references

Continue reading