n8n-expression-syntax

To fix n8n expression syntax errors, ensure all expressions are wrapped in double curly braces {{ }} and use proper quoting for field or node names containing spaces. Verify you reference correct structures like $json.body for webhooks and exact node name casing.

n8n webhook data often does not show up because it is nested inside the $json.body structure. You must access it using the correct path like {{$json.body.name}} to retrieve nested fields, arrays, and payload data from incoming webhook requests.

To reference data from another node in n8n expressions, use the $node variable with the exact node name in quotes, such as {{$node["HTTP Request"].json.data}}. Ensure the node name casing matches exactly to prevent runtime errors.

Yes, you can use environment variables in n8n workflow expressions by referencing them with the $env variable. Ensure your expression syntax is correctly enclosed in {{ }} braces, such as {{$env.MY_VARIABLE}}, to route data securely.

Common mistakes when writing n8n expressions for API calls include missing double braces, incorrect webhook .body structure references, and failing to quote node names with spaces. Validating syntax against real-world scenarios prevents these runtime errors.