- No date yetn8n 3.0
n8n 3.0: what breaks in your workflows
n8n 3.0 has no release date yet; its breaking-changes page says 3.0.0 is available as an early access release. Workflows that use a removed node fail, and published ones stop activating.
What breaks
The removed nodes include the legacy Function, Function Item and Item Lists nodes, Cron and Interval (use Schedule Trigger), HTML Extract, Read PDF, Workflow Trigger (use n8n Trigger) and AI Transform. Version 1 of the AI Agent node and Edit Image versions 1 and 1.1 are gone as well. In expressions, $getPairedItem is removed; use $('<node-name>').item, .itemMatching() or .pairedItem().
I checked all 14,139 public templates in the n8n gallery offline: 7.9% break on 3.0, and those templates hold 26.1% of all template views.
How to fix it
On a running instance, Settings > Migration Report lists the affected workflows. If you keep exported workflow JSON in a repo, the scanner reads each *.json file with n8n nodes and names every node and expression to change, with its replacement.
Check a repository for this
Exported n8n workflow JSON: removed nodes, removed node versions and removed expression helpers.
The same rules run offline in atokim4/n8n-v3-check (MIT).
Sources
Dates and wording re-read on the official pages on . Vendors move dates; the official page wins.