n8n-expression-syntax

Craft correct n8n expressions with syntax patterns and fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and debugging n8n expressions is error-prone due to the required {{}} syntax, nested paths, and webhook data structure under .body. This guide helps users adopt correct expression usage, avoid common pitfalls, and follow best practices to build reliable workflows.

Core Features & Use Cases

  • Formal expression syntax: Learn the standard {{expression}} pattern and how to apply it across $json, $node, $now, and $env.
  • Webhook data handling: Understand that webhook data is inside .body and how to access it in expressions.
  • Node reference patterns: Correctly reference data from other nodes with $node["Node Name"].json and quote names with spaces.
  • Debugging & validation: Use the expression editor, error messages, and quick fixes to resolve issues quickly.
  • Use cases: Compose dynamic messages, format dates, manipulate strings, and build data-driven alerts.

Quick Start

Experiment with a simple expression like Hello {{$json.body.name}} in the expression editor to see real-time results.

Frequently Asked Questions about n8n-expression-syntax

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

FAQPage Schema
How do I access webhook data in n8n expressions?

Access webhook data in n8n expressions by targeting the `.body` property, such as `{{$json.body.name}}`. This ensures you correctly extract payload fields from incoming webhook requests for dynamic workflow content.

Why does my n8n expression syntax keep failing?

n8n expressions fail when the standard `{{expression}}` syntax is broken or nested paths are incorrect. Use the expression editor to validate references, ensure proper bracket closure, and apply fixes for common syntax mistakes.

How do I reference data from other nodes in n8n workflows?

Reference data from other nodes using the `$node["Node Name"].json` pattern. Always quote node names containing spaces to ensure the expression correctly retrieves data across your workflow.

What's the best way to debug n8n expressions?

Debug n8n expressions by leveraging the expression editor for real-time validation and reviewing error messages. This approach helps identify incorrect node references, syntax issues, and malformed webhook data paths quickly.

Can I format dates and manipulate strings in n8n expressions?

Format dates and manipulate strings in n8n expressions using variables like `$now`. This allows you to compose dynamic messages and build data-driven alerts directly within your workflow nodes.