n8n-expression-syntax

To access webhook data correctly in n8n expressions, reference the payload under the body object using {{$json.body.email}} instead of the incorrect {{$json.email}} pattern to prevent data access errors.

The correct syntax for n8n expressions wraps dynamic variables in double curly braces like {{$json}} or {{$now}}, ensuring the workflow engine parses your dynamic content without syntax errors.

Your n8n workflow expression fails when using incorrect syntax or accessing non-existent top-level fields, which can be fixed by validating expression patterns and using core variables like $json and $node correctly.

n8n expression syntax uses {{ }} patterns to inject dynamic variables into node fields, while Code node syntax requires writing full JavaScript to manipulate data arrays and objects directly.

Yes, you can access environment variables in n8n workflow expressions using the {{$env}} variable pattern, allowing you to securely inject external configuration values into your automation workflows.

To reference output from a previous node in an n8n expression, use the {{$node}} variable combined with the node name and desired field, or use {{$json}} to access the incoming data directly.