What problem does it solve?
n8n expression errors and brittle data references waste time by producing wrong or non-deterministic results when workflows branch, refactor, or clear item context.
Core Features & Use Cases
- Node-name references over $json: Use $('Node Name').item.json.field to keep data stable across refactors, branching, and context-clearing nodes.
- Safe, maintainable expression patterns: Prefer Luxon for date math, inline expressions in consumers instead of extra nodes, and format multi-line logic with comments.
- Correct iteration behavior: Use executeOnce appropriately when leveraging $source.all().map/filter/reduce aggregations inside expressions.
- Type-safe returning with ={{ ... }}: Ensure objects/arrays/booleans/numbers aren’t accidentally treated as strings when fields require structured types.
Quick Start
Ask for expressions that reference upstream nodes by name, use Luxon for date operations, and avoid $json in branched workflows so the result remains correct after refactors.