n8n-expression-syntax

Validate n8n expression syntax and fix common {{}} errors in workflows.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/accutrust1688-maker/accu --skill n8n-expression-syntax-accutrust1688-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-expression-syntax
Source: https://github.com/accutrust1688-maker/accu/tree/main/skills/n8n-expression-syntax
Command: npx skills add https://github.com/accutrust1688-maker/accu --skill n8n-expression-syntax-accutrust1688-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Error-prone expression syntax in n8n workflows; this guide helps users identify and fix common mistakes when using the {{}} syntax to access $json, $node, $now, and $env variables, and clarifies webhook data structure.

Core Features & Use Cases

  • Comprehensive rules for correct expression syntax, including required quotes for spaces, proper node references, and avoiding double-wrapping.
  • Practical examples showing how to access nested fields, arrays, and webhook body data; supports debugging and validating expressions in real workflows.
  • Use Case: Build reliable automation by validating expressions before deployment and quickly correcting misreferences in complex workflows.

Quick Start

Enter a test expression in the editor, such as {{$json.body.name}} or {{$node["HTTP Request"].json.data}}, and verify the evaluated result in the expression editor.

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 invalid n8n expression syntax when referencing webhook data?

Fix invalid n8n expression syntax by ensuring proper use of {{}} wrapping and correct data references. Verify webhook body data is accessed using safe patterns like {{$json.body.name}} to prevent evaluation errors in your workflows.

Why does my n8n expression fail when accessing nested fields in $json?

n8n expressions fail when nested fields in $json lack required quotes for spaces or use double-wrapping. Apply consistent reference patterns and validate syntax in the expression editor before deployment to resolve misreferences.

What is the correct way to reference another node's data in n8n expressions?

The correct way to reference another node's data in n8n expressions is using proper node references like {{$node["HTTP Request"].json.data}}. Ensure syntax avoids double-wrapping and follows frontmatter rules for error-free workflow execution.

Can I validate n8n expressions for $env and $now variables before running the workflow?

You can validate n8n expressions for $env and $now variables by entering test expressions in the editor. Verify the evaluated result directly in the expression editor to debug and correct syntax errors before workflow deployment.

What are common limitations when using double-wrapping in n8n expression syntax?

Double-wrapping in n8n expression syntax causes evaluation failures by creating invalid nested brackets. Avoid wrapping {{}} inside another {{}} and ensure single, clean references to $json or $node variables for reliable workflow execution.

How do I handle spaces in field names when writing n8n expressions?

Handle spaces in n8n expression field names by using required quotes around the reference. Apply consistent syntax rules like {{$json["field name"]}} instead of dot notation to avoid syntax errors and ensure accurate data access in workflows.