n8n-expression-syntax

To fix incorrect n8n expression syntax, wrap dynamic values referencing $json or $node in {{ }} within target node fields to enforce proper evaluation and prevent workflow errors.

Your n8n webhook expression fails because webhook data must be accessed via the correct .body structure. Referencing the payload directly without specifying .body causes the node to miss the incoming data and throw evaluation errors.

The correct way to handle spaces in n8n expressions is by applying proper quoting around variable references. Wrapping dynamic fields with {{ }} and ensuring accurate syntax for spaces prevents parsing mistakes during node execution.

To debug n8n workflow expressions, apply a systematic debugging framework to inspect $json, $node, $now, and $env references. Verify safe node references, check webhook .body structures, and validate {{ }} syntax to spot mistakes quickly.

Yes, you can use $env and $now variables inside n8n node expressions across workflows. Composing correct expressions for these variables ensures accurate environment data and timestamp retrieval without triggering syntax validation errors.