Skip to content
SkillModel-led6,063 tokens in use

n8n Expression Syntax

A guide to writing correct n8n expressions: double braces, $json and $node, the webhook body trap, a native-node-first order, JMESPath, helpers and silent null errors.

6,686 stars on the repository MIT Licenseczlonkowski/n8n-skills · skills/n8n-expression-syntax
/plugin install czlonkowski/n8n-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing n8n Expression Syntax costs

103tokens idle
6,063tokens in use
11,631tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure19/25
  • Examples15/15
  • Output15/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity88
  • Maintenance92
  • Community60
  • Maturity36
  • Momentum40

n8n Expression Syntax is a skill for Claude that covers the {{ }} expressions n8n uses to pass data between nodes. It explains the core variables $json, $node, $now, $env and $vars, the rule that webhook data sits under body, and quoting for names with spaces.

It also sets an order for transforming data: the service’s own node, a native node, a short expression, and only then a Code node. It documents $jmespath quoting rules, built-in helper methods and the way runtime errors inside an expression resolve to null.

What You Get

  • The braces, quoting and exact-name rules for expressions, with a fix table for common mistakes
  • A description of $json, $node, $now, $env and $vars, including when $env is blocked
  • The webhook output structure and the rule that user data is under body
  • A four-step gatekeeper: service node, native node, short expression, Code node
  • A table of $jmespath quoting rules and a table of helper methods such as pluck, sum, unique and diffTo
  • Advice on removing Set nodes that only rename fields and anchoring converging branches with a NoOp

Common Use Cases

  • Fixing a webhook field that resolves to undefined because the path skips body
  • Referencing a node whose name has spaces or different casing
  • Choosing between an expression, a native node and a Code node for a transform
  • Querying nested JSON for one value with $jmespath
  • Finding out why a Filter drops every item after an expression error

What Makes It Unique

Beyond syntax, it ships tested guidance on what fails quietly: JavaScript errors inside braces become null, wrong $jmespath quoting returns an empty array, and a Python or Code step can pass items through. It orders the options for a transform so Claude picks a native node before code, and it explains that complex expressions cost little per item.

Under The Hood

The skill is instructions and two reference markdown files, with no scripts. It tells Claude to use the n8n-mcp tools to validate workflows and to patch nodes through partial updates, which call your n8n server. It does not fetch web pages or run commands itself. The expressions it teaches run inside n8n when a workflow executes and can read item data, other nodes’ output and environment variables when the instance allows them.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers