Skip to content

n8n 3.0 lands in early December and 1.x support ends on 31 December. Will your workflows break?

By Bilal Haider, Founder, Theepa Studio · · 5 min read

Short answer

n8n released the 3.0 beta on 27 October 2026 and says the stable release follows in early December. Support for n8n 1.x ends on 31 December 2026, and 1.x users must upgrade to 2.x before 3.x. The move to 3.x is one way and removes older nodes such as Function, Item Lists and Read PDF, so run the Migration Report and test on a copy before you switch.

What changes in n8n 3.0, and when?

n8n announced version 3.0 on its community forum on 23 October 2026 and released the 3.0.0 beta on 27 October 2026. Its blog says the stable release follows in early December. It has not given an exact day. Four dates matter:

DateWhat happensWho it affects
27 October 20263.0.0 beta (early access) releasedTeams that want to test early
Early December 2026Stable 3.x releasedEvery n8n user
31 December 2026Support for 1.x endsTeams still on n8n 1.x
12 months after stable 3.x2.x stops getting security and critical bug fixesTeams that stay on 2.x

n8n says the 3.0 changes apply to everyone: free self-hosted, Cloud, and Enterprise or Business. Two rules shape any plan. There is no direct path from 1.x to 3.x, so 1.x users must upgrade to 2.x first. And the move to 3.x is one way. n8n's own words: "There's no going back to 2.x."

Will my n8n workflows break in 3.0?

Some will. n8n's breaking-changes page says workflows that use a removed node fail when they run. The removed list includes nodes that many older workflows still rely on:

  • Function and Function Item
  • Item Lists
  • Cron and Interval
  • HTML Extract, Read PDF and the binary file read and write nodes
  • the legacy OpenAI nodes, OpenAI Assistant and OpenAI Model
  • AI Transform, and version 1 of the AI Agent node

Other changes are quieter but can still stop a workflow:

  • The default time limit for a Code node task drops from 5 minutes to 1 minute.
  • Unverified community nodes are turned off by default.
  • The Slack API credential now needs a signing secret.
  • Encryption key rotation is on by default.
  • Chat Hub is off by default, and n8n says version 4.0 removes it.

Does this affect n8n Cloud or only self-hosted n8n?

Both, in different ways. Self-hosted teams carry the biggest change: n8n 3.0 no longer supports installs run with npm or npx, and n8n will not publish a runnable package to npm. If you installed n8n with npm on a small server, plan a move to Docker. On first start, 3.0 also renames the binaryData folder to storage, and n8n will not start if both folders exist.

On Cloud, n8n's docs say the instance owner chooses which version the instance runs, that n8n asks for confirmation before a major version, and that updates cannot be rolled back. The removed nodes apply on Cloud too, so the workflow checks below matter just as much.

How do I find which workflows need work?

n8n added a Migration Report to the editor, at Settings > Migration Report, on version 2.39 or later. It scans your instance and lists the workflows and instance settings that 3.0 changes. Owners and admins see every workflow and an Instance issues tab. Other users see only the workflows they can edit. The report can migrate some nodes automatically, but n8n says the automatic migration covers node changes only. Settings and credentials are still on you.

If nobody on your team owns n8n, this is the point where a list of flagged workflows turns into a project. Our AI workflows and automation service starts with a map of every workflow, fixes what the upgrade breaks and leaves your team a setup it can run.

Worked example: a small agency on self-hosted n8n 1.x

This is a hypothetical scenario, not a client.

A five-person agency runs n8n 1.x, installed with npm on a small cloud server. It has 12 workflows: website form to CRM, a weekly client report built with a Function node, an invoice reader that uses Read PDF, Slack alerts, and a social post drafter on the legacy OpenAI node.

  1. 1This week: back up. Export every workflow, copy the database and the data folder, and store the encryption key somewhere safe.
  2. 2Move to 2.x on Docker before 31 December. Support for 1.x ends that day and 3.0 drops npm installs, so rebuild the install with Docker on the current 2.x release. Our advice: pin an exact version number rather than a moving tag, so nothing upgrades by surprise.
  3. 3Run the Migration Report. It should flag the Function, Read PDF and legacy OpenAI workflows, plus the Slack credential.
  4. 4Fix on a copy. Rebuild each flagged step with a supported node, add the Slack signing secret, and time any Code step that may run past a minute.
  5. 5Test 3.x on a second instance. When stable 3.x ships in early December, restore the backup to a test server, upgrade it and run each workflow with real test data.
  6. 6Switch, then keep the backup. Upgrade production in mid December and keep the 2.x backup, because 3.x cannot be rolled back.

Should I upgrade, stay on 2.x or switch tools?

Your situationOur advice
On 1.xMove to 2.x now. Support ends on 31 December 2026
On 2.x with few flagged workflowsUpgrade to 3.x in December after testing on a copy
On 2.x with many flagged workflows and no timeStay on 2.x for now. It gets security and critical fixes for 12 months after stable 3.x
Self-hosting has become a burdenCompare n8n Cloud with other tools before you rebuild anything

If you are weighing other tools, our comparison of Pipedream Workflows alternatives covers n8n, Zapier, Make and custom code side by side.

What should I do this week?

  1. 1Check your n8n version in Settings. If it starts with 1, plan the move to 2.x first.
  2. 2Back up workflows, the database, the data folder and the encryption key.
  3. 3On 2.39 or later, open Settings > Migration Report and export the list.
  4. 4Note every workflow that uses a removed node, Slack, or a long Code step.
  5. 5Book a test day for early December, when stable 3.x ships.

Sources

Bilal Haider

Founder, Theepa Studio

Bilal founded Theepa Studio in 2016. The studio has delivered more than 10,000 brand identities for companies in the US, UK and the GCC.

Questions people also ask

When is n8n 3.0 released?

n8n released the 3.0.0 beta on 27 October 2026. Its blog says the stable release follows in early December 2026, without an exact day.

When does support for n8n 1.x end?

On 31 December 2026. n8n says there is no direct path from 1.x to 3.x, so 1.x users should upgrade to 2.x first.

Can I roll back from n8n 3.0 to 2.x?

No. n8n says moving to 3.x is one way, and its Cloud docs say updates cannot be rolled back. Keep a full 2.x backup and test 3.x on a copy first.

Can I still install n8n with npm?

Not from 3.0. n8n's breaking-changes page says 3.0 no longer supports installs run with npm or npx, so self-hosted teams should move to Docker.

Keep reading

Tell us what you're building.

A 30-minute call. We look at your brand and site together, and you leave with a plan and a fixed price, whether or not you hire us.