Find where your workflow will break.

Paste an n8n workflow or a LangGraph graph. We read the file itself, not a guess about it, and show every place it cannot work as written: a field no step produces, a node that never runs before the one that reads it, a branch that can never be taken, a side effect done twice on a retry. Each one names the nodes and says why.

Check a workflow Free. No account. Nothing is stored.

What each one looks like

Missing field

“Create Contact” reads a field its input never has

It reads “company” from the item it is given, and no node that feeds it produces that field. The expression will be empty at run time.

Lead Hook → Shape Lead → Is Paid → Create Contact

What it checks

Fields and names. An expression that reads a field no earlier step produces, or names a node that does not exist or never runs before it.
Paths. Nodes no trigger reaches, triggers that start nothing, loops with no way out, a merge waiting for two inputs that cannot both arrive, a graph node with no way to the end.
Conditions. An IF or a filter whose answer the workflow itself fixes, so one side never runs.
Side effects and time. A retried step that sends or creates something, a public webhook that leads to one, a wait longer than the schedule that starts the run.

It reads what the file says. What a Code node computes or what an outside service returns is not in the file, so where a step's output cannot be known, nothing is concluded about it.