Unverified60% confidenceFactExact time
In n8n, data between nodes is exposed through the $json object, for example {{ $json.email }} retrieves the email field in the current node's input data; to reference data from a node that is not the direct upstream, one can use the syntax $node["node name"].json.field name.
2
Sources
60%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedn8n's Form node is a built-in trigger node; after running, it generates a publicly accessible form page link, and after a user submits the form, the output is a JSON object containing each field's value, with field names being the key names referenced by subsequent nodes.74% 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.69% similarUnverifiedWhen 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.69% similarUnverifiedn8n expressions allow embedding notation like {{ $json.email }} in node fields, supported by built-in JavaScript syntax, and can do simple string concatenation, date formatting, and conditional checks.68% similarVerifiedSwitching to the Input tab in the n8n node editing panel allows you to preview in real time the complete JSON structure flowing into that node67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016740API
curl https://kongchang.com/api/v1/knowledge/claims/1016740MCP
get_claim(id=1016740)