How do I access data from a specific node in n8n?

Use the $node variable with bracket notation for the node name, for example: {{$node["Node Name"].json.field}}.

How do I handle webhook data that isn't showing up?

Webhook nodes wrap incoming data in a .body object. Ensure you are accessing it via {{$json.body.yourField}} rather than {{$json.yourField}}.

Why does my n8n expression appear as literal text?

This typically occurs when the required double curly braces {{ }} are missing. n8n treats any text outside of these braces as a literal string.

Can I use n8n expression syntax inside a Code node?

No. Code nodes use direct JavaScript. You should use $json.field or $input.item.json.field instead of the {{ }} expression syntax.

n8n Expression Syntax Validator

Name: n8n Expression Syntax Validator
Author: ProfSynapse

byProfSynapse

•

Productivity & Workflow

Validates and fixes n8n expression syntax to ensure accurate data mapping and error-free workflow automation.

About

The n8n Expression Syntax skill is an expert utility designed to help developers write, validate, and troubleshoot dynamic expressions within n8n workflows. It provides deep logic for handling double-curly brace syntax, accessing variables via $json and $node, and correctly navigating nested webhook structures where data is frequently misplaced. Whether you are formatting dates with Luxon, concatenating strings for API requests, or debugging 'undefined' property errors, this skill ensures your automation logic adheres to n8n's specific execution environment requirements.

Key Features

36 GitHub stars
Automatic validation of double-curly brace {{}} expression syntax
Correct path resolution for webhook data nested under the .body property
Context-aware guidance for $json, $node, $now, and $env variables
Bracket notation enforcement for node and field names containing spaces
Syntax differentiation between n8n expression fields and JavaScript Code nodes

Use Cases

Dynamically referencing data from previous nodes in a multi-step automation
Formatting complex timestamps and date math using Luxon within expressions
Fixing 'undefined' errors when mapping data from Webhook or HTTP Request nodes

About

Key Features

36 GitHub stars
Automatic validation of double-curly brace {{}} expression syntax
Correct path resolution for webhook data nested under the .body property
Context-aware guidance for $json, $node, $now, and $env variables
Bracket notation enforcement for node and field names containing spaces
Syntax differentiation between n8n expression fields and JavaScript Code nodes

Use Cases

Dynamically referencing data from previous nodes in a multi-step automation
Formatting complex timestamps and date math using Luxon within expressions
Fixing 'undefined' errors when mapping data from Webhook or HTTP Request nodes