Skip to content

n8n workflow doctor

Check an n8n workflow without running it: nodes, connections, expressions and secrets. Get fixes and improvements you accept or reject. Free, in your browser.

AvailableIn your browserInput: Data

How to use: n8n workflow doctor

  1. Export your workflow from n8n (⋯ menu → Download) and drop the .json here, or paste the JSON into the box.
  2. Press “Analyse workflow” and pick the mode: Check (diagnosis), Repair (proposed changes) or Optimize (improvements and a plain-language flow).
  3. Open each finding, accept or reject the proposed changes, review the new score and download the report or the proposed JSON.

What it accepts and what you get

Input
An n8n workflow .json file (or its pasted text) of up to 5 MB and 2000 nodes.
Output
A report with a score, findings per node (error, warning, information, security risk), proposed changes with a before/after view, and downloads of the report (.md) and the proposed JSON.
Where your data is processed
The analysis runs in your browser: the workflow is not uploaded or stored, and nothing is executed or imported into any n8n. Only if you turn on AI repair, after showing you what will be sent, a secret-free copy goes to the provider you choose, with your own key.

Limitations and notes

  • The analysis is static and runs in your browser: no node is executed, no n8n is contacted and the file is not uploaded or stored.
  • Secrets found in the JSON are not displayed: they are detected by shape and hidden on screen, in the report and in anything that would go to an AI.
  • Check and the fixed-rule fixes work without a key. AI repair is optional, uses YOUR API key and the provider may charge you; before sending you see exactly what goes out. It has not yet been verified against a live provider.
  • Items marked “hypothesis” may or may not fail when run; only a real run confirms it. A clean result does not guarantee the workflow works, and an AI repair can be wrong even if it passes validation.
  • It knows the main n8n nodes; a community or very new node is flagged as “unrecognised”, which is not necessarily a fault.

Frequently asked questions

Is my workflow uploaded to a server?

No. It is read and analysed in your browser. Only if you turn on the AI and tick the consent box is a copy without credentials or secrets sent to the provider you choose, straight from your browser.

Do I need an API key?

Not for checking or for the fixed-rule fixes. Only AI repair or AI optimisation ask for your own key; this site supplies none and pays for nobody.

Can it import the fixed workflow into my n8n?

No: this tool never connects to n8n. Download the proposed JSON, test it on a copy and import it yourself.

When to use it

  • When an imported workflow throws an error and you do not know where to start looking.
  • Before sharing or publishing a workflow, to make sure it holds no keys written inside.
  • To review someone else's workflow before running it on your server.

Examples

A broken connection
If a node points to another that no longer exists, it shows as an error with the node name and an option to remove that connection.
A key inside the JSON
It shows as a security risk with its location and length, never the value; move it into an n8n credential.
Sturdier
In Optimize you can accept retries for an HTTP call and see the re-validated score before downloading.

Common mistakes

  • Assuming the workflow is fine because there are no warnings: it is a static analysis and runs nothing.
  • Accepting an AI change without reading the before/after and without testing it on a copy of n8n.
  • Sharing the original JSON believing it is clean: the report hides secrets, but the original file keeps them.

Related tools