Why isn't my $json variable working in a webhook node?

In n8n webhook nodes, incoming data is nested under the .body property. You must use {{$json.body.fieldName}} instead of {{$json.fieldName}} to access your payload.

Can I use n8n expressions inside a Code node?

No, n8n Code nodes use standard JavaScript. You should use $json.field or $input.item.json.field directly without curly braces or the '=' prefix.

How do I handle spaces in node names within expressions?

When a node name contains spaces, you must use bracket notation with double quotes, such as {{$node["HTTP Request"].json.data}}.

Is n8n expression syntax case-sensitive?

Yes, node references are case-sensitive. The name inside the $node brackets must exactly match the name of the node in your workflow canvas.

n8n Expression Expert

Name: n8n Expression Expert
Author: sromeroubisos

bysromeroubisos

0•

Productivity & Workflow

Validates and fixes n8n expression syntax to ensure reliable workflow automation and correct data mapping.

This skill provides comprehensive guidance on the specific syntax required for n8n expressions, helping developers navigate the nuances of double curly braces, variable scoping, and the often-misunderstood webhook data structure. It acts as a real-time validator to prevent common errors like incorrect node referencing, missing braces, or misuse of expressions within Code nodes, ensuring workflows execute flawlessly across different node types and environments.

Key Features

01Provides date formatting templates using Luxon through the $now variable

02Validates double curly brace syntax for dynamic content mapping

03Identifies contexts where expressions should be avoided like Code nodes or credentials

04Corrects webhook data access patterns using the body property

05Standardizes node references with proper quotes and case sensitivity

060 GitHub stars

Use Cases

01Formatting timestamps and performing date math for API requests

02Correctly mapping nested data from previous nodes using the $node variable

03Troubleshooting 'undefined' property errors in n8n automation nodes

Key Features

01Provides date formatting templates using Luxon through the $now variable

02Validates double curly brace syntax for dynamic content mapping

03Identifies contexts where expressions should be avoided like Code nodes or credentials

04Corrects webhook data access patterns using the body property

05Standardizes node references with proper quotes and case sensitivity

060 GitHub stars

Use Cases

01Formatting timestamps and performing date math for API requests

02Correctly mapping nested data from previous nodes using the $node variable

03Troubleshooting 'undefined' property errors in n8n automation nodes