Industry updates · 4 min read
Still on n8n 1.x? Support ends 31 December 2026: are you ready for 3.0?
Published
n8n 3.0 is in beta, the stable release follows in early December, and support for 1.x ends on 31 December 2026. What changes, what may break, and the 4 checks to run before you move.

If your business runs automations on n8n, version 3.0 is on its way, and the upgrade only goes one direction. n8n released the 3.0.0 beta on 27 October 2026, and says the stable release follows in early December1. Support for version 1.x ends on 31 December 2026.
This is n8n’s own announcement of a beta, and the full list of breaking changes, with what to do for each, sits in its documentation rather than in the post. Here is what the post says, what may break, and the checks worth running before you move. The habit holds for any workflow tool you rely on, n8n, Make or Zapier alike: read the vendor’s list before a big version, not after.
What is changing in version 3.0?
Version 3.0 is not about new features. It clears out old parts, makes security settings stricter by default, and changes how n8n runs behind the scenes.
n8n saves breaking changes (updates that may need you to change your workflows or settings) for a new major version, and 3.0 brings them together. The ones a business is most likely to feel:
- Old building blocks removed. The Function, Function Item, Item Lists, Cron and Interval nodes are gone, along with the legacy OpenAI node and older AI Agent modes. Most have a direct replacement and many migrate automatically: Function becomes the Code node, and Cron and Interval give way to the Schedule Trigger.
- A shorter time limit for code. The default Code node timeout drops from 5 minutes to 1 minute, and it can be changed.
- Self-hosting on Docker. If you run n8n on your own server, installing with npm or npx is no longer supported; Docker (software packaged in a sealed container) is the way. Kubernetes and Helm setups are not affected.
- Safer defaults. For example, Slack credentials now need a signing secret, and unverified community packages are off by default.
The changes apply to the self-hosted Community edition, Cloud, and Enterprise or Business alike.
Will your workflows break?
Some may, and you can find out which before you move. n8n’s Migration Report lists the workflows and settings that 3.0 affects.
Every instance on version 2.39 or later has it under Settings > Migration Report. It fixes many issues automatically and saves each fix as a new workflow version for you to review and publish, while your published workflows keep running on version 2. Admins see every workflow; other users see the ones they can access.
The part to plan around: the move to 3.x is one way. In n8n’s words, “There’s no going back to 2.x”, and going back means restoring a backup.
If you are still on 1.x, there is no direct path to 3.x: upgrade to 2.x first. After the stable release, 2.x keeps getting security and critical bug fixes for 12 months, while new features ship on 3.x only.
Our view: 2.x gives you some room, 1.x does not. The 31 December 2026 date is close, and a 1.x setup needs 2 steps to reach 3.x.
What should you do before you upgrade?
Follow n8n’s own path: update, check, back up, test. Then upgrade the copy your business runs on.
- Update to the latest 2.x and open the Migration Report. The latest 2.x carries the newest version of the report.
- Fix, or mark “won’t fix”, everything it flags. The report helps by filtering out workflows that are not published or have not run in a long time.
- Take a full backup.
- Upgrade a test or staging copy first, then production.
We would add 2 checks of our own. If you self-host with npm, plan the move to Docker as its own job, not a side step of the upgrade. And look for code steps that may run longer than 1 minute: with the new default limit, they need the setting changed or the step split.
Want to try it early? Cloud users can pick 3.0.0 Beta (early access) when changing version, and self-hosted users install it like any other beta. Do it on a test copy, never on the one your customers depend on.

Get new updates
Articles, news and offers from NightForward.
Researched and drafted with AI tools, fact-checked against the sources below, and edited by Kringle Lam.
Sources
- n8n, Introducing n8n 3.0 (opens in a new tab) (27 October 2026)