n8n-expression-syntax

n8n webhook expression syntax errors often occur because payload data is not accessed from the correct path. You must extract incoming request data using the .body property, such as {{$json.body.name}}, to ensure the webhook payload is properly evaluated.

Referencing another node in n8n expressions requires correct bracket notation for names with spaces. You must use the syntax {{$node["HTTP Request"].json.data}} to access outputs from previous nodes, ensuring the node name string is exact and properly quoted.

n8n expressions show as plain text when dynamic variables are not properly wrapped in curly braces. You must enclose variables like $json, $node, $now, and $env within {{}} so the n8n expression editor evaluates them as dynamic content instead of literal strings.

Accessing environment variables in n8n syntax uses the $env variable within curly braces. You must format your n8n expression as {{$env.VARIABLE_NAME}} to securely inject environment configurations into your workflow nodes without exposing them in plain text.

Handling spaces in node names within n8n expressions requires bracket notation. You must use square brackets and quotes around the node name, like {{$node["My Custom Node"].json.field}}, to ensure the expression parser correctly targets the intended workflow node.

Yes, n8n expression validation covers common pitfalls in code nodes by enforcing best practices for data access. It provides troubleshooting tips to prevent syntax mistakes when handling $json arrays and nested fields within your custom workflow logic.