n8n-expression-syntax

To access webhook payload data in n8n expressions, reference the field using {{$json.body.fieldName}}. A common mistake is using {{$json.fieldName}} directly, which fails because webhook data is nested inside the body structure of the incoming JSON data.

n8n expression syntax uses double curly braces {{ }} to inject dynamic values directly into node parameters, whereas code node JavaScript allows writing standalone scripts. Confusing the two leads to syntax errors when attempting to run complex logic inline within standard workflow nodes.

Use variables like $json, $node, $now, and $env in n8n workflows by wrapping them in curly braces such as {{$now}}. These core variables allow you to reference incoming data, previous node outputs, current timestamps, and environment variables respectively for dynamic content generation.

n8n expressions fail when referencing another node's data if the node name is incorrect or the output structure is misunderstood. Validate node referencing by ensuring the target node has executed successfully and using the correct $node['NodeName'].json syntax to access its payload.

Yes, you can use n8n expressions to dynamically generate content for automated emails by inserting variables like {{$json.body.email}} into node parameters. This ensures personalized data from previous workflow steps, such as webhook payloads, is accurately passed to email sending nodes.

You do not need to write custom JavaScript to manipulate webhook data in n8n if the transformation is simple. Expression syntax handles basic dynamic data access and string interpolation directly within node fields, preventing the need for a separate code node for straightforward variable replacements.