Unverified50% confidenceFactExact time
Execution retention and timeout settings of an n8n workflow are not preserved through ordinary JSON import and must be manually checked and set in the editor's Settings.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedNever put credentials in the exported workflow JSON; instead configure them through the n8n credential system and grant only the minimum permissions.75% similarUnverifiedn8n workflow JSON usually does not include credentials (such as API Key or OAuth authorization), so after pasting, users still need to complete the account connection themselves.72% similarUnverifiedPersonal/lab and customer environments must use separate n8n instances (at least separate credentials and networks), workflow JSON change control should be treated the same as middleware configuration, writing from a laptop to production SAP must never be allowed, and backup workflow definitions should be exported and managed as code.70% similarVerifiedn8n workflows are stored in JSON format and are version-trackable68% similarUnverifiedTo avoid rigid approval processes, it is recommended to externalize approval rules as configuration tables (such as JSON or database routing rule tables), maintained by business personnel rather than developers, so that adding roles or adjusting thresholds requires no changes to the workflow itself.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1068544API
curl https://kongchang.com/api/v1/knowledge/claims/1068544MCP
get_claim(id=1068544)