When you build automated workflows with n8n, you need to write expressions inside double curly braces. These expressions let you pull data from one step to the next. Many people make mistakes with the syntax, especially when working with webhook data. This guide helps you write correct expressions and fix common errors.
The most common error is forgetting to wrap variables in {{ }}. Without them, n8n treats your text as a literal string. Another big mistake is assuming webhook data is at the root. Remember that webhook data lives under .body.
You can access $json for the current node's output and $node to reference other nodes. Node names must be in quotes and case-sensitive. Use $now for timestamps and $env for environment variables. Avoid using expressions inside Code nodes. This skill will save you time and reduce errors.
Global
mkdir -p ~/.claude/skills/n8n-expression-syntaxProject
mkdir -p .claude/skills/n8n-expression-syntaxSource Repository
Lark Drivelarksuite/cli
Organize Lark cloud files import export manage permissions and versions
Lark Eventlarksuite/cli
Stream Lark events in real time with simple CLI commands
Lark Workflow Meeting Summarylarksuite/cli
Turn your Lark meeting notes into organized weekly summaries with ease
Lark Approvallarksuite/cli
Easily manage Lark approval instances and tasks from your command line
Implementmattpocock/skills
Implement PRD or issue tasks with TDD tests typechecking and review
Executing Plansobra/superpowers
Load a plan review critically then execute each task with verifications
Subagent Driven Developmentobra/superpowers
Execute plans with fresh subagents per task and thorough reviews for fast iteration
Churn Preventioncoreyhaines31/marketingskills
Reduce customer churn with smart cancel flows and failed payment recovery