Unverified50% confidenceFactExact time
When n8n imports workflow JSON, some nodes (such as HTTP Request credential selection and Error Trigger associations) depend on instance-local resource IDs, and after cross-instance import they become empty references or point to the wrong objects.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedn8n JSON generated by large language models does not always import successfully on the first attempt; node version differences, credential references, and specific node parameter structures can all cause errors after pasting.79% similarUnverifiedThe HTTP Request node supports authentication methods such as Bearer Token, Basic Auth, and OAuth2, and the returned JSON data is automatically parsed by n8n into referenceable fields.77% 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.75% similarVerifiedn8n encapsulates each integration capability as an independent node, with JSON data streams passed between nodes, supporting custom logic in JavaScript/TypeScript.71% similarUnverifiedThe node coordinates position and node id in the workflow JSON change when dragging in the UI, copying and pasting, or in certain n8n version upgrades.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1056871API
curl https://kongchang.com/api/v1/knowledge/claims/1056871MCP
get_claim(id=1056871)