Check an export before you share it
Select one n8n workflow JSON file, then run a local structural check for common review blockers and fields that deserve manual inspection.
Choose a workflow export
No file selected.
Technical limits: one workflow object, maximum file size 5 MB, maximum nesting depth 30, and maximum 50,000 inspected fields per node.
Local report
| Check | Location | Category | Why review it |
|---|
No targeted fields were detected. This is not proof that the export is safe to share.
What this check covers
It counts nodes and flags exports above the 25-node review limit. It locates credential references, pinned data, endpoint fields, authentication-related fields, and expressions that may draw from workflow input, other nodes, environment variables, or credentials. It never includes detected values, node names, credential names or arbitrary field keys in the report.
n8n’s own export and import documentation warns that exported workflow JSON includes credential names and IDs, and that HTTP Request nodes imported from cURL may contain authentication headers. A credential reference is not automatically a leaked secret, but its name may still be sensitive.
USD 35 written review
One redacted n8n workflow of up to 25 nodes, its expected result, and one input/output example. Written findings within two business days after scope and start-date agreement, with one clarification round. Review only: no production access, credentials, video call, or repair.
Discuss the USD 35 review on n8n Community →
To check fit, reply there with your approximate node count, the expected result, and the one issue you want reviewed. Please start with a description only: do not post your workflow, customer data or credentials publicly.
Prefer email? Request the review by email. We agree scope, payment arrangements and start date in writing before work begins.