n8n-expression-syntax

Fix n8n expression syntax errors by wrapping references in double curly braces and accessing webhook payloads through the `.body` property. Properly structuring webhook data locations ensures accurate data extraction and prevents common validation failures during workflow execution.

The correct syntax for using $json and $node variables in n8n workflows requires enclosing them in double curly braces. This notation allows cross-node references and data mapping, ensuring the platform parses the dynamic variables correctly without throwing syntax validation exceptions.

An n8n webhook expression returns undefined when the syntax misses double curly braces or targets the wrong data location. Webhook payload data resides under `.body`, so accessing it directly without this property reference causes empty data retrieval and failed downstream node execution.

Validate n8n expressions using $now and $env by applying syntax rules and testing reference patterns before execution. Checking that environment variables and current timestamps are wrapped in double curly braces ensures the workflow editor parses dynamic values correctly and prevents runtime errors.

The best way to debug cross-node references in n8n expressions is enforcing double curly braces around $node variables and verifying data paths. Using validation test scenarios and quick reference patterns helps identify structural mistakes and ensures accurate data mapping between nodes.