n8n Workflow Inspector
Upload or paste an exported n8n workflow JSON file to map its nodes and connections, find broken references, review expression links, and check for potentially hard-coded sensitive values before sharing or moving a workflow.
1. Load an n8n workflow
Choose a standard single-workflow JSON export from n8n, or paste its JSON contents below. The selected file is read in this browser and is not uploaded.
Limits: one standard workflow JSON at a time, up to 10 MB and 500 nodes. This version does not open .n8np packages, credential exports, execution data or n8n database backups.
Inspection coverage
- Draws the workflow graph from the exported nodes and connection map.
- Checks whether connection sources and destination node names exist.
- Finds isolated nodes, disconnected components and duplicate node names or IDs.
- Checks common expression references such as
$("Node name")and$node["Node name"]. - Counts credential references without displaying credential names, IDs or secret values.
- Flags selected fields that may contain hard-coded authorization values, tokens or passwords.
2. Workflow overview
Visual workflow map
Solid lines show main connections. Dashed lines show other connection types, such as AI tools or model connections. Node positions use the exported editor coordinates when available; otherwise the inspector creates a simple left-to-right layout.
Workflow checks
| Severity | Check | Finding | Location |
|---|---|---|---|
| Run an inspection to see findings. | |||
Node inventory
| Node name | Node type | Credential references | Connections in | Connections out | Expression references |
|---|---|---|---|---|---|
| No nodes inspected yet. | |||||
3. Download review files
Download a findings report, or create a separate redacted workflow copy for sharing. The original text remains unchanged in the editor.
The redacted file is intended for review or sharing. It may no longer be import-ready because credential references or sensitive settings can be changed.
What is the n8n Workflow Inspector?
The n8n Workflow Inspector is a browser-based utility for reviewing a standard n8n workflow JSON export. It reads the workflow's node list and connection map, then creates a visual overview and a set of static checks that can help you review the workflow before sharing it, documenting it or moving it to another n8n instance.
What does the workflow checker validate?
Nodes and connections
The inspector checks that connection sources and destination node names exist in the exported node list. It also reports duplicate node names or IDs, isolated nodes and separate connected components. Branches and loops are not automatically treated as errors because they can be valid workflow designs.
Expressions and node references
Common references to another node in expressions are scanned for names that do not appear in the workflow. This is a heuristic check: expressions can be generated dynamically, and not every n8n expression form can be fully evaluated by a static browser tool.
Credential references and sensitive values
Credential references are counted without displaying their names or IDs. The inspector also looks for selected literal values in fields commonly used for passwords, tokens, API keys and authorization headers. It reports the JSON path, not the value itself. This scan cannot guarantee that every secret is found.
How to use the n8n workflow inspector
- In n8n, open the workflow menu and download or export the workflow as JSON.
- Choose the JSON file above, or paste the JSON text.
- Select Inspect workflow to draw the graph and run the checks.
- Review missing connections, expression references, disconnected nodes and security findings.
- Download the audit report or create a redacted copy for sharing.
Do not upload credential export files or decrypted credential backups to this page. Use only a workflow JSON export. Review the redacted copy before sharing it; automated detection is not a substitute for a manual security review.
Frequently asked questions
Does this tool connect to my n8n instance?
No. It only reads the JSON you paste or select. It does not connect to n8n, call workflow nodes or transmit the file to a server.
Does an n8n workflow export contain credential secrets?
Standard workflow exports normally store credential references rather than the credential secret values. However, credential names and IDs may be present, and literal values entered directly into node parameters—such as authorization headers—can be included. Review the exported JSON before sharing it.
Can this tool find every hard-coded secret?
No. It checks selected key names and common token patterns. Custom fields, encoded values, dynamically generated values and unfamiliar secret formats may not be detected. A clean report does not prove that the workflow contains no sensitive information.
Why does the tool report a disconnected node?
A node may not be linked to another node in the exported connection map, or it may belong to a separate component. This can be intentional while editing a workflow. Review the node in the n8n editor before removing it.
Does it validate whether nodes will execute successfully?
No. The tool does not execute nodes, evaluate every expression, test credentials, inspect external services or reproduce n8n runtime behavior. It performs structural checks on the exported JSON only.
Can I inspect an n8n package or credentials export?
This version is designed for a standard single-workflow JSON export. It does not parse .n8np packages, decrypted credential exports, execution history or n8n database backups.
Official n8n reference
See the n8n workflow export and import documentation for instructions on exporting and importing workflow JSON.