Old syntax that no longer works in n8n
- Feb 13
- 1 min read
What this means (non-technical)
The expression: $items is older syntax that was used in expressions and Code nodes to access data from previous nodes.
In newer versions of n8n, this pattern is considered outdated and replaced by clearer, more structured ways to reference data.
If you are still using: $items, your workflow relies on legacy behavior.
What usually goes wrong
Older syntax can:
Break after upgrades.
Behave differently than expected.
Make expressions harder to read and maintain.
Confuse team members who learned the newer syntax.
Over time, this creates small friction points. The workflow still works, but it becomes harder to confidently upgrade or change.
You may hesitate to update n8n because you are unsure what will break.
When this becomes urgent
This becomes urgent when:
You upgrade to newer n8n versions.
Expressions start failing unexpectedly.
You share workflows with others using updated syntax.
You maintain long-lived production workflows.
The longer legacy syntax remains, the more fragile future upgrades become.
Detect issues in your n8n workflows
|
Definitions
Deprecated syntax: An older way of writing something that is still supported but may be removed in the future.
Expression: Dynamic logic inside {{ }} used to reference data between nodes.
Disclaimer
This article highlights common patterns and risks seen in real-world n8n workflows. It’s meant to help you build more confidently and avoid surprises as your automation grows. Behavior can vary depending on your setup, version, and configuration.