Connection secrets should live in the approved credential mechanism for the connection, not in ordinary examples, planning notes or business payloads. n8n documents credentials as securely stored authentication information used to connect workflows to external services. That does not establish the safety of every place a secret might be copied.
Distinguish a reference from a secret
A descriptive label such as “training-register-test-connection” identifies a connection without reproducing its authentication value. A pasted password or access token is the sensitive value itself.
As editorial advice, keep design documents focused on labels, owners, purposes and required operations. Do not ask teammates to paste live secrets into a review sheet. A credential reference is useful for discussing architecture; a working secret usually is not.
n8n also documents creation in a personal space or project where supported. Verify the appropriate scope for your environment rather than assuming every deployment has identical options.
Perform a secret-location audit
List each location that might receive connection information:
- Credential storage: identify the owner and intended connection without recording the value.
- Workflow examples: replace authentication values with clearly fake placeholders.
- Handover notes: record setup responsibilities, not passwords.
- Request payloads: ask whether authentication information is required there by the connected provider.
- Troubleshooting output: determine whether sensitive values could be reproduced.
- Screenshots or copied messages: review before sharing them internally.
For each location, mark “reference only,” “synthetic placeholder,” “sensitive value required,” or “unnecessary sensitive copy.” Assign an owner to investigate every unresolved entry.
This is a proposed audit process, not a claim that n8n automatically detects or removes exposed values.
Evaluate a hypothetical handover
Consider a hypothetical Pune team handing over a test automation. Its notes contain a connection label, a fake token reading EXAMPLE-NOT-VALID, and a copied request containing a real authentication value.
The label and unmistakably fake placeholder serve the handover purpose. The real value fails the review because the team has not established why that copy is necessary or who can access it.
Evaluate the handover by asking whether another authorised maintainer can understand the design without receiving a secret in the document. Use only synthetic business records during this review, never customer or private material.
Stop unnecessary copying before rollout
Stop distribution if a real secret appears in a location without a justified purpose. Ask the responsible security owner to assess exposure and decide the appropriate remediation; deleting one copy is not evidence that all copies are gone.
When reviewing the automation catalog, check access format and save terms before buying. Marketplace account, code or token offers do not prove official subscription equivalence or suitable credential controls.
Sources and scope
Source material checked 29 October 2026; features/policies may change. The n8n credential documentation establishes credential purpose, secure storage and supported creation scopes. The location audit and handover assessment are editorial advice, not security guarantees.