Pinned data detected in n8n
Why test data left in workflows increases size and may expose sensitive information
What is this issue?
Pinned data is test output that has been fixed to a node for debugging purposes. While useful during development, pinned data remains in the workflow JSON and gets exported, shared, and deployed along with the workflow.
Problems with pinned data:
•Test data containing real customer information•Large datasets pinned to multiple nodes•Outdated test data that doesn't match current schemas•Credentials or tokens visible in pinned responses
Why is this dangerous?
Increased workflow size
Pinned data can be megabytes large, slowing down workflow loading and editing.
Sensitive data exposure
Test data may contain real PII, credentials, or business data that gets shared with exports.
Misleading test results
Pinned data overrides real inputs, potentially masking bugs during testing.
Memory overhead
Large pinned data consumes n8n memory when loading workflows.
How to fix it
- 1
Clear pinned data before deployment
Before deploying or exporting, unpin all data from nodes by clicking the pin icon.
- 2
Review pinned data for secrets
Check if any pinned data contains credentials, tokens, or PII before sharing workflows.
- 3
Use test workflows
Keep test data in separate test workflows rather than pinning to production workflows.
- 4
Add to deployment checklist
Include 'clear pinned data' in your deployment process to prevent accidental exposure.
Scan your workflow now
Upload your n8n workflow JSON and detect nodes with pinned data that should be cleared.