GP-SOP-008 | Workflow Quality
Test an n8n Workflow Before You Share It
A tested workflow export that another person can import without receiving your credentials or private data.
When to use this SOP
Use this before publishing, selling, handing off, or moving an n8n workflow to another environment.
What you need
- The working n8n workflow
- Representative sample inputs
- A clean test environment when possible
- Installation and usage notes
The procedure
Follow these steps
- 01
Run a successful sample using ordinary input and save the expected output.
- 02
Test empty, malformed, unusually long, and partially missing input.
- 03
Confirm errors stop safely and explain what the user should correct.
- 04
Review every node for credentials, tokens, email addresses, file paths, IDs, URLs, personal data, and environment-specific values.
- 05
Export the workflow and inspect the JSON as plain text for private or machine-specific information.
- 06
Import the scrubbed JSON into a clean n8n instance and reconnect credentials from scratch.
- 07
Compare the clean test output with the saved expected output.
- 08
Update the requirements, installation steps, customization notes, and troubleshooting guide.
Human checkpoint
Stop and review before continuing
A dropdown that recognizes credentials in your own n8n instance does not prove the export contains secrets. The clean import test is what matters.
Definition of done
- Happy-path and failure inputs were tested
- Errors are understandable
- The JSON contains no credentials or private data
- A clean import succeeds
- Requirements and expected outputs are documented
When the process gets stuck
If the workflow only runs on the original machine, identify each environmental dependency and replace hidden assumptions with setup instructions.
Where automation fits
Contract tests can validate node structure and sample outputs, but manual secret review and a clean import remain required.