n8n-expressions
Skill1 starsChanged 3 months agoMITView on GitHub
Use when writing or debugging n8n expressions (`{{ }}`), `$json`, `$('Node')`, `$input`, Luxon/DateTime, field mapping, or "expression error" / wrong data after Merge.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- LucasGS520/Claude-Skillstheir own version, first seen Sep 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- LucasGS520/Claude-Skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- n8n-agentsSkill
- n8n-ai-seo-geo-automationSkill
- n8n-binary-dataSkill
- n8n-code-nodesSkill
- n8n-credentials-securitySkill
- n8n-data-tablesSkill
- n8n-debuggingSkill
- n8n-error-handlingSkill
- n8n-loopsSkill
- n8n-mcp-toolingSkill
- n8n-node-configurationSkill
- n8n-production-opsSkill
- n8n-subworkflowsSkill
- n8n-workflow-lifecycleSkill
- using-n8n-skillsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Expressions over extra nodes: when the transform is local to one parameter.
- Very specific: line 41
When branches converge and downstream needs a stable ref, insert a NoOp named e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
n8n Expressions
Author: Taghi Molavi
Non-negotiable
Prefer $('Node Name').item.json.field (or .first() / .last() / .all()) over bare $json for anything that must survive refactors.$json breaks silently when intermediates, Aggregate, certain Code modes, or Merge change item context.
Strong defaults
- No single-consumer Set nodes — inline the expression at the destination unless 2+ consumers share a heavy derivation or the Set is a sub-workflow output shaper.
- Luxon in expressions for dates —
{{ DateTime.now().minus({ days: 7 }).toISO() }}— avoid DateTime node unless the user wants it visible. - Expressions over extra nodes when the transform is local to one parameter.
- Multi-line expressions: indent + short comments (many n8n users are not engineers).
Core APIs
{{ $json.email }}
{{ $('Fetch User').item.json.id }}
{{ $input.all() }}
{{ $input.first().json }}
{{ $now }} {{ $today }}
{{ DateTime.fromISO($json.created).toFormat('yyyy-LL-dd') }}
{{ $json.items.map(i => i.name).join(', ') }}Merge / branch stability
When branches converge and downstream needs a stable ref, insert a NoOp named e.g. Combine Inputs and reference $('Combine Inputs').
Common failures
| Symptom | Likely cause |
undefined field | Wrong node name, or used $json after context clear |
| Works in test, fails in prod | Different item counts / empty branch |
| Expression error luxon | Invalid ISO string; guard with ternary |
| Array treated as object | Need .first() or explicit index |
Pair with
n8n-code-nodeswhen expression length/complexity explodesn8n-debuggingfor silent wrong values
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

