n8n-expression-syntax

Write n8n expressions using {{}} syntax with $json.body and $node references.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Alkan-ia/Alkan-ia.github.io --skill n8n-expression-syntax-alkan-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-expression-syntax
Source: https://github.com/Alkan-ia/Alkan-ia.github.io/tree/main/n8n-skills/skills/n8n-expression-syntax
Command: npx skills add https://github.com/Alkan-ia/Alkan-ia.github.io --skill n8n-expression-syntax-alkan-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

n8n users often struggle to craft correct expressions and interpret webhook data structures, leading to silent errors and misrouted data in workflows.

Core Features & Use Cases

  • Clear guidance on using the {{}} expression syntax in various nodes.
  • Demonstrations of accessing webhook data via {{$json.body...}} and $node references.
  • Debugging and best practices for reliable workflows with real-world examples.

Quick Start

  • Open a workflow and wrap dynamic content with {{}}.
  • Validate expressions in the editor and fix common mistakes using examples provided in EXAMPLES.md.
  • Review webhook data access patterns and node references to ensure data is retrieved from the correct paths.

Frequently Asked Questions about n8n-expression-syntax

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

FAQPage Schema
How do I write n8n expressions to access webhook data correctly?

To access webhook data in n8n expressions, wrap dynamic content with {{}} syntax and retrieve payload fields using typical data paths like {{$json.body...}}. This ensures correct data extraction from incoming webhook requests and prevents silent workflow errors.

What is the correct syntax for referencing other nodes in n8n workflows?

Reference other nodes in n8n workflows using the $node syntax within standard {{}} expression brackets. This approach allows you to retrieve dynamic output from preceding nodes, ensuring accurate data routing across your automation scenarios.

Why does my n8n expression return undefined or fail silently?

n8n expressions fail silently when data paths are incorrect, often because webhook data is not accessed under the .body property. Validate expressions in the editor and troubleshoot common errors by verifying paths like $json to ensure data is retrieved correctly.

Can I use bracket notation to access dynamic fields in n8n expressions?

Yes, you can use bracket notation within n8n expression syntax to access dynamic or nested fields safely. Combining bracket notation with {{}} wrappers allows precise extraction of variable data structures across real workflow scenarios.

What are the best practices for debugging n8n expression syntax errors?

Best practices for debugging n8n expression syntax include validating dynamic content wrapped in {{}} directly within the editor and reviewing webhook data access patterns. Follow ready-to-use examples to fix common mistakes and ensure reliable workflow data retrieval.