How do I access data from a node with spaces in its name?

Use bracket notation with quotes, for example: {{$node["HTTP Request"].json.data}} instead of standard dot notation.

Can I use these expressions inside an n8n Code node?

No, Code nodes use direct JavaScript. Use $json.field or $input.item.json.field without the curly braces.

Why does my n8n expression appear as literal text?

This usually happens because the double curly braces {{ }} are missing. Ensure your expression is wrapped correctly to be evaluated by n8n.

Why can't I access my Webhook data directly via $json?

In n8n, Webhook nodes wrap incoming data under a .body property to preserve headers and params. Use {{$json.body.yourField}} instead of {{$json.yourField}}.

n8n Expression Syntax Expert

Name: n8n Expression Syntax Expert
Author: ProfSynapse

byProfSynapse

•

Productivity & Workflow

Validates and repairs n8n workflow expressions to ensure accurate data mapping and error-free automation.

About

This skill provides comprehensive guidance for writing, debugging, and optimizing expressions within n8n workflows. It specializes in the double-curly-brace {{}} syntax, mapping complex data structures from previous nodes using $json and $node variables, and correcting common mistakes like incorrect webhook data paths or case-sensitivity issues in node names. By enforcing best practices for Luxon date formatting and bracket notation for spaced names, it helps developers build more resilient automation logic.

Key Features

Guidance on using Luxon-powered $now for advanced date formatting
Accurate syntax for referencing external workflow nodes with $node
Identification of contexts where expressions should be avoided, such as Code nodes
Validation of double curly brace {{}} expression syntax
40 GitHub stars
Correct pathing for Webhook node data under .body properties

Use Cases

Troubleshooting 'Cannot read property of undefined' errors in n8n workflows
Correctly mapping incoming webhook payloads to downstream notification nodes
Dynamically formatting dates and timestamps for external API requests

About

Key Features

Guidance on using Luxon-powered $now for advanced date formatting
Accurate syntax for referencing external workflow nodes with $node
Identification of contexts where expressions should be avoided, such as Code nodes
Validation of double curly brace {{}} expression syntax
40 GitHub stars
Correct pathing for Webhook node data under .body properties

Use Cases

Troubleshooting 'Cannot read property of undefined' errors in n8n workflows
Correctly mapping incoming webhook payloads to downstream notification nodes
Dynamically formatting dates and timestamps for external API requests