n8n-expression-syntax

Access webhook data in n8n expressions by targeting the body property of the webhook output. User data sent to the webhook resides under the body path, so referencing $json.body ensures correct payload extraction and avoids common data path mistakes.

Referencing data from other nodes in n8n workflows requires exact node name casing and proper quoting for spaces. Use standard expression syntax with double curly braces to resolve cross-node variables like $node dynamically across your workflow scenarios.

n8n expression syntax fails inside a Code node when dynamic expression patterns are used unnecessarily. You should avoid wrapping standard JavaScript variables in double curly braces within Code nodes, as this causes syntax parsing errors during workflow execution.

Use $json and $node variables in n8n workflow expressions by wrapping them in double curly braces for dynamic content. These core variables allow you to access incoming JSON payloads and reference data outputs from preceding nodes across typical workflow scenarios.

Common n8n expression mistakes include incorrect webhook body nesting, failing to quote node names with spaces, and misusing expressions inside Code nodes. Validating syntax patterns against core variables like $json and $node prevents these frequent workflow debugging issues.

You can use environment variables and timestamps in n8n expressions by referencing $env and $now within double curly braces. These core variables resolve dynamically during workflow execution to inject secure environment configurations and current time data into your nodes.