skills.rest
contenido-wq
contenido-wqCOMMUNITY
Explore all skills by this author →
GitHub

n8n-expression-syntax

Corrects n8n expression syntax and variable access paths in workflows.

Updated May 12, 2026
Search Tags:#n8n#data binding#node reference#expression syntax#webhook payload#debugging undefined
One-click install
npx skills add https://github.com/contenido-wq/aivi_core --skill n8n-expression-syntax-contenido-wq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: n8n-expression-syntax
Source: https://github.com/contenido-wq/aivi_core/tree/main/.github/skills/n8n-expression-syntax
Command: npx skills add https://github.com/contenido-wq/aivi_core --skill n8n-expression-syntax-contenido-wq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

n8n workflows often fail or return undefined values because expressions are formatted incorrectly or because webhook payload data is accessed from the wrong location.

Core Features & Use Cases

  • Correct expression formatting: Ensure expressions are wrapped in double curly braces and avoid invalid brace patterns.
  • Reliable variable access: Use the right context variables ($json for current node data, $node for other nodes, $now for timestamps, and $env for environment variables).
  • Webhook payload troubleshooting: Prevent the most common failure by accessing user data under $json.body.* instead of assuming it exists at the root.

Quick Start

Use the n8n-expression-syntax skill to check the exact expression you’re using in your workflow and correct both syntax and data-path mistakes.

Frequently Asked Questions about n8n-expression-syntax

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

FAQPage Schema
Why does my n8n webhook expression return undefined values?▼

n8n webhook payload data must be accessed via $json.body.* instead of the root object. Accessing webhook user data from the wrong location causes expressions to return undefined values.

How do I fix n8n expression syntax showing literal output?▼

Literal output in n8n expressions occurs when syntax is formatted incorrectly. Wrap your expressions in double curly braces and avoid invalid brace patterns to evaluate variables correctly.

What context variables should I use for data binding in n8n nodes?▼

Use $json for current node data, $node for other nodes, $now for timestamps, and $env for environment variables. Selecting the correct context variable ensures reliable data binding across workflow nodes.

How do I reference n8n node names with spaces in expression fields?▼

Reference n8n node names with spaces using correct quoting and bracket notation. Node names are case-sensitive, so matching the exact syntax prevents variable access path failures.

Related Skills

Explore More Software Engineering Skills→
muid-nihalmuid-nihal

n8n-expression-syntax

Validate n8n expression syntax and fix common errors in workflows.

Community
Intermediate
HustleDanieHustleDanie

n8n-expression-syntax

Diagnoses and fixes n8n expression syntax errors in {{ }} code.

Community
Intermediate
MorrisLu-TaipeiMorrisLu-Taipei
84

n8n-expression-syntax

Validate and correct n8n expression syntax for node fields and webhook payloads.

Community
Intermediate
Gingi892Gingi892

n8n-expression-syntax

Validate and fix n8n expression syntax errors in workflow fields.

Community
Advanced