n8n-expression-syntax

Validate and repair n8n expression syntax for workflow node data.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edupazogle/agentic_cockpit --skill n8n-expression-syntax-edupazogle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: n8n-expression-syntax
Source: https://github.com/edupazogle/agentic_cockpit/tree/main/.agents/skills/n8n/n8n-expression-syntax
Command: npx skills add https://github.com/edupazogle/agentic_cockpit --skill n8n-expression-syntax-edupazogle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents workflow failures caused by incorrect n8n expression syntax, especially when referencing webhook payloads and data from other nodes.

Core Features & Use Cases

  • Correct expression formatting: Ensures dynamic values use double curly braces and avoids common mistakes like missing braces or extra nesting.
  • Accurate data-path targeting: Validates how to read fields from the current node, referenced nodes, and webhook outputs (notably that webhook user data is typically under .body).
  • Reliable node and field access: Guides correct usage of $node["Node Name"] with exact case-sensitive names and bracket notation for keys with spaces or special characters.
  • Safer troubleshooting habits: Covers when expressions should not be used (e.g., Code nodes, webhook paths, credential fields) and how to interpret frequent error symptoms.

Quick Start

Use the n8n-expression-syntax skill to validate an expression you’re putting into a node field for a workflow that maps webhook data into later nodes.

Frequently Asked Questions about n8n-expression-syntax

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix n8n expression errors when mapping webhook payload data?▼

To fix n8n expression errors when mapping webhook payloads, ensure user data is accessed under the `.body` path and that expressions are properly wrapped in `{{ }}` double curly braces to pass data between workflow nodes correctly.

Why does my n8n expression fail when referencing outputs from another node?▼

n8n expressions fail when node outputs are referenced incorrectly if you do not use exact case-sensitive names and quotes, such as `$node["Node Name"]`, to query data from previous workflow nodes.

Can I use n8n expression syntax inside a Code node?▼

You cannot use n8n expression syntax inside Code nodes, webhook paths, or credential fields. These are non-expression contexts where dynamic values must be handled differently without wrapping them in `{{ }}` braces.

What is the correct syntax for accessing spaced keys in n8n workflow expressions?▼

The correct syntax for accessing spaced or special keys in n8n workflow expressions requires bracket notation. This prevents workflow failures by ensuring accurate data-path targeting when reading fields from current or referenced nodes.