n8n-expression-syntax

Validate n8n expression syntax and fix common errors in workflows.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/Test-perelman/Mailtrix --skill n8n-expression-syntax-test-perelman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-expression-syntax
Source: https://github.com/Test-perelman/Mailtrix/tree/main/n8n-skills/skills/n8n-expression-syntax
Command: npx skills add https://github.com/Test-perelman/Mailtrix --skill n8n-expression-syntax-test-perelman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users ensure n8n expressions are correctly formatted, preventing runtime errors and misinterpretations of data in workflows.

Core Features & Use Cases

  • Validate and troubleshoot n8n expression syntax ({{}}) across workflows.
  • Provide clear guidance on accessing data with $json, $node, and handling webhook payloads (e.g., using .body).
  • Reference common mistakes with fixes and practical examples to speed up development and reduce debugging time.

Quick Start

Open your workflow, edit a field that uses an expression, and verify that:

  • all dynamic content is wrapped with {{ }} (except in Code nodes),
  • webhook data is accessed via {{$json.body...}},
  • node references use $node["Node Name"].json, with exact case and quotes for spaces.

Frequently Asked Questions about n8n-expression-syntax

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

FAQPage Schema
What is the correct way to use $json in n8n expressions?

Use $json in n8n expressions to access the JSON output of the previous node. Wrap the reference in {{ }} braces, such as {{$json.fieldName}}, to dynamically insert data into your workflow fields and ensure correct syntax validation.

How do I access webhook payload data using n8n expressions?

Access webhook payload data in n8n expressions by referencing $json.body. When processing incoming webhooks, use the syntax {{$json.body...}} to correctly extract fields from the HTTP request payload without runtime errors.

Why does my n8n expression fail when referencing another node's data?

Your n8n expression fails because node names are case-sensitive and require exact matching. Use the syntax $node["Node Name"].json, ensuring you use bracket notation and enclose node names with spaces in quotes to prevent data misinterpretation.

Can I use n8n expressions inside a Code node?

You cannot use n8n expressions inside a Code node. Code nodes execute raw JavaScript, so wrapping dynamic content in {{ }} braces causes misuse and errors; restrict expression syntax to regular workflow nodes.

What is the correct way to use $json in n8n expressions?

Use $json in n8n expressions to access the JSON output of the previous node. Wrap the reference in {{ }} braces, such as {{$json.fieldName}}, to dynamically insert data into your workflow fields and ensure correct syntax validation.