n8n-expression-syntax

Validate and fix n8n expression syntax errors in workflow fields.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Gingi892/automation-shamai --skill n8n-expression-syntax-gingi892
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-expression-syntax
Source: https://github.com/Gingi892/automation-shamai/tree/main/skills/n8n-expression-syntax
Command: npx skills add https://github.com/Gingi892/automation-shamai --skill n8n-expression-syntax-gingi892

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill teaches you how to write correct n8n expressions using the double-curly-brace syntax, diagnose common mistakes, and reliably access data from webhook payloads and other nodes to build robust workflows.

Core Features & Use Cases

  • Validate and correct expressions in fields across n8n nodes, including $json, $node, $now, and $env.
  • Illustrate the critical Webhook data structure (data under .body) and how to reference it in expressions.
  • Provide a comprehensive catalog of common mistakes with clear fixes, plus real-world workflow examples.
  • Distinguish between using expressions in regular fields and direct data access in Code nodes, to prevent misusage.

Quick Start

Test with the expression {{$json.body.name}} to see the corrected syntax and fixes for common mistakes.

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 common n8n expression syntax errors in workflow fields?

To fix n8n expression syntax errors, validate your double-curly-brace syntax and ensure correct referencing of variables like $json, $node, $now, and $env. This process identifies common mistakes and provides clear corrections to build robust workflows.

How does n8n webhook data structure work when referencing payloads in expressions?

n8n webhook data structure places incoming payload information under the .body property. You reference this data in expressions using the syntax {{$json.body.name}} to accurately access and pass webhook payloads within your workflow fields.

What is the difference between n8n expressions and Code node data access?

n8n expressions use double-curly-brace syntax to reference variables like $json in standard workflow fields, whereas Code node data access involves direct JavaScript data manipulation. Separating these usage patterns prevents common misusage and workflow errors.

Why is my n8n expression not working when I reference $json or $node?

Your n8n expression is likely not working due to incorrect double-curly-brace syntax or invalid node references. Validating frontmatter requirements and checking the catalog of common mistakes helps diagnose and resolve these specific data access errors.

Can I use environment variables and timestamps in n8n workflow expressions?

Yes, you can use environment variables and timestamps in n8n workflow expressions by referencing $env and $now. Validating these references ensures frontmatter requirements are met and provides practical examples for reliable workflow automation.