n8n-expression-syntax

To fix n8n expression syntax errors, ensure you wrap dynamic content in {{ }} and reference $json correctly, such as {{$json.body.name}}. Proper handling of $json, $node, and bracket notation for spaces prevents common workflow mistakes.

The correct syntax for referencing webhook data in n8n expressions involves using {{$json.body}} to access incoming payload fields. Applying bracket notation for fields with special characters ensures accurate data extraction from webhook triggers.

Building multi-node references requires using the $node object to access data from previous workflow steps. You must enforce correct syntax like {{$node["Node Name"].json.field}} to prevent expression evaluation errors across nodes.

n8n expressions break with spaces because dot notation fails to parse them correctly. You must apply bracket notation, like {{$json["field name"]}}, to properly access fields containing spaces or special characters.

Yes, you can use $now and $env variables inside n8n workflow expressions to inject current timestamps and environment variables. Correctly wrapping them in {{ }} ensures they evaluate properly within your workflow nodes.

The best way to validate n8n expressions is to type an expression like {{$json.body.name}} in a node field to check its syntax and see the evaluated value. This prevents common errors before executing the full workflow.