n8n-expression-syntax

Validate and correct n8n expression syntax for workflow data access.

9|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/CarbeneAI/Forge --skill n8n-expression-syntax-carbeneai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-expression-syntax
Source: https://github.com/CarbeneAI/Forge/tree/main/.claude/skills/n8n-expression-syntax
Command: npx skills add https://github.com/CarbeneAI/Forge --skill n8n-expression-syntax-carbeneai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and fix common errors in n8n expression syntax, ensuring proper use of {{}} and correct data access patterns for $json, $node, and webhook bodies.

Core Features & Use Cases

  • Validate and correct n8n expressions across workflows, including complex nesting and array access.
  • Provide guidance for webhook data with the correct path under .body and safe use of $node references.
  • Includes comprehensive examples and best practices to reduce mistakes and improve debugging efficiency.

Quick Start

Open a workflow, enter an expression using {{}} to access data, and test against a webhook payload to see the evaluated result.

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 syntax errors in my workflow?

Fix n8n expression syntax errors by wrapping variables in double curly braces, quoting node names with spaces, and maintaining exact case sensitivity for node references. This validation prevents common workflow failures.

Why does my n8n webhook expression not access the payload data?

n8n webhook expressions fail when the data path is incorrect. Access webhook payloads by targeting the .body property within your expression to properly retrieve incoming JSON data from the trigger node.

How do I use $json and $node variables in n8n expressions?

Use $json and $node variables in n8n expressions by enclosing them in {{ }} syntax. Ensure node names with spaces are quoted and match exact casing to avoid reference errors during workflow execution.

What is the correct syntax for n8n expressions with nested braces?

Correct n8n expression syntax avoids nested braces entirely. Wrap the entire expression in a single set of {{ }} and use standard JavaScript syntax inside to access data without causing parsing errors.

Can I use $now and $env variables in n8n workflow expressions?

Yes, you can use $now and $env variables in n8n workflow expressions. Wrap them in {{ }} syntax to correctly evaluate current timestamps and environment variables within your automated workflows.

What causes n8n expressions to break when referencing other nodes?

n8n expressions break when referencing other nodes if the node name contains spaces but is not wrapped in quotes, or if the node name casing does not match exactly. Validate references to prevent workflow errors.