A shared automation export can expose credentials through node parameters, URLs, headers, names, and sample data. Inspect the artifact itself rather than assuming platform-managed credentials make every exported workflow safe to share.
Export review covers more than secret stores
An automation export contains workflow structure and configuration, and may include references or values entered directly into nodes. Screenshots, examples, pinned execution data, and support attachments can carry additional sensitive information.
n8n’s export documentation warns about credential names and identifiers and possible authentication headers in imported HTTP requests. Use that as a prompt to review the actual file, not as a complete list of every sensitive field.
For a proposed sharing process, create a sanitised copy with placeholders, fictional examples, and a separate configuration manifest. Keep the working private version under its existing controls. Do not overwrite the only recoverable live configuration while preparing a public example.
Inspect a fictional HTTP automation
A workflow uses a managed CRM credential, but one HTTP node contains a manually pasted bearer token and a customer-specific URL. The export also includes a real contact note used during debugging. Removing only the managed credential reference leaves both disclosures.
The review should check structured secret fields, known token patterns, URLs, free-text examples, and synthetic markers. A second reviewer or automated scanner can assist, but no pattern scanner guarantees that every confidential business value is detected.
| Export element | Review action |
|---|---|
| Headers and query values | Remove secret and personal values |
| Credential labels | Replace revealing customer-specific names |
| Sample execution items | Use approved fictional data |
| Webhook URLs | Evaluate whether they expose capability or internal context |
| Environment manifest | Include variable names without secret values |
Import the sanitised artifact into an isolated environment and verify that it fails safely until explicitly configured. A demonstration should not retain hidden access to the source client.
Handle discovered exposure as a separate task
If a real secret was shared, deleting the file may not remove copied versions. Follow the organisation’s incident and credential-rotation process. Do not claim that redacting the latest export retracts earlier disclosure.
Sanitisation adds preparation time but makes handover and examples more reusable. Keep a checklist tied to the supported platform and update it when new node types or export formats introduce additional fields.
This sharing process is proposed. The voice integration case study describes related backend work. Pair it with workflow migration review.
Automation export FAQ
Are credential IDs the same as secret values?
Not necessarily, but labels and references can still reveal private context and need review.
Can a workflow be shared safely by removing one token?
Inspect every sensitive path and sample artifact, not only the first obvious secret.
What should recipients receive?
A sanitised definition, fictional fixtures, required configuration names, scope limitations, and safe setup expectations.