n8n workflow JSON export: a 10-step preflight checklist
Before handing an automation to a client, check the export, dependencies, credentials, side effects and test evidence. This guide is free to use, with no email gate.
Written by Askoure Systems, seller of the optional paid auditor. Not affiliated with n8n. Static inspection cannot certify a workflow's runtime behavior, safety or compatibility.
Three checks before any import
Try python -m json.tool workflow.json on your local export. A parse failure means it is not valid JSON.
Confirm sources and destinations named in connections have corresponding nodes.
Check which credentials, community nodes, variables and services must exist on the destination.
The 10-step n8n export preflight
- 01
Work from a safe, sanitized copy
Keep your original export protected. Before sharing even a sample, check node parameters, expressions and pinned data for secrets, personal data and customer payloads.
- 02
Verify the JSON structure
Open the plain export and confirm that nodes is an array and connections describes the graph. Try python -m json.tool workflow.json locally. Optional metadata depends on the n8n version.
- 03
Trace source and target connections
Check each connection name against nodes in the export. Review error branches and downstream side effects. A disconnected node may be intentional.
- 04
List credential rebinding needs
Credential labels in an export do not prove that the target instance has valid credentials. Rebind using the destination owner's least-privilege credentials.
- 05
Note environment dependencies
Capture required environment variables, webhook URLs, community node packages, linked workflows, n8n version and external services.
- 06
Look for unsafe placeholders
Review test endpoints, dummy IDs, hard-coded paths, token-like values and assumptions about incoming data. A text search cannot serve as a comprehensive secret audit.
- 07
Review pinned or example execution data
Inspect pinData and examples to avoid shipping personal data. Remove private payloads from anything shared outside the team.
- 08
Import into a non-production instance
Confirm the graph renders and the needed node types and variables are available. Do not enable live triggers or customer-facing writes yet.
- 09
Run real success and failure tests
With test accounts, check normal input, invalid/empty input, API limits, idempotency of side effects, retries, alert recipients and rollback.
- 10
Record handoff acceptance
Note export version, credential owner, prerequisite setup, tests performed, remaining risks, rollback plan and the client's acceptance.
Keep a short acceptance record: source/version, credentials rebound, prerequisites, test executions, unresolved risks, owner sign-off and rollback steps.
Want to automate selected structural checks?
The n8n Workflow Preflight Auditor — $9 is a separate offline HTML utility for plain JSON exports. It includes fictional clean/broken examples, regression tests, a report and a client handoff checklist.
Not included: live workflow execution, credential access checks, automatic code repair, complete secret scanning or production certification. You still need the manual checks and real test execution above.
Sources and further reading
The original free checklist on GitHub, official n8n workflow sharing guidance and execution-history documentation.
Questions about one reproducible Python/API/JSON defect? Request a free written scope check. The separate code-only commission does not include remote n8n setup.