Platform deadlines · n8n

n8n 1.x support ends on December 31, 2026

53 days left (UTC).

n8n has no direct upgrade path from 1.x to 3.x: you move to 2.x first. n8n 3.0 removes legacy nodes, and published workflows that still use one stop triggering.

What n8n has announced

Support for n8n 1.x ends on December 31, 2026. source
The n8n 3.0 beta came out on October 27, 2026. The stable 3.x release is planned for early December 2026, with no exact day announced. source
There is no direct path from 1.x to 3.x: upgrade to 2.x first. source
After 3.0 becomes stable, 2.x keeps receiving security and critical bug fixes for 12 months. source
n8n Cloud: self-serve instances still on v1 at the deadline will be upgraded to v2 automatically. source
Self-hosted: n8n 3.0 requires a Docker-based deployment. Installing with npm or npx n8n is no longer supported. If you already run your own Docker Compose file, you don't need to switch. source
There is no direct rollback from 3.x to 2.x. Going back means restoring a full backup. source

What breaks in n8n 3.0

n8n's own words: “Workflows that use a removed node fail when they run.” A published workflow that uses one “doesn't activate when n8n 3.0 starts, so its triggers stop firing.” source

Removed in 3.0	Replacement stated by n8n
Function, Function Item	Code node
Item Lists	Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize, depending on the operation
Cron, Interval	Schedule Trigger node
HTML Extract	HTML node, Extract HTML Content operation
Read PDF	Extract from File node, Extract From PDF operation
Workflow Trigger	n8n Trigger node
Manual Chat Trigger	Chat Trigger node
LangChain Code	No direct replacement

This is a selection. The full list, with every node and helper removed, is on the n8n breaking changes page. source

What to do before December 31, 2026

Check your version. In n8n, open Settings, then Personal: the version number appears at the bottom of the left sidebar.
If you are on 1.x, upgrade to 2.x. Do not try to jump straight to 3.x.
On 2.39 or later, open Settings, then Migration Report, and review both tabs: workflow issues and instance issues. If you do not see this option, update to 2.39 or later first.
Replace every removed node listed by the report with its replacement.
Self-hosted on npm or npx: move to Docker before upgrading to 3.0.
Take a full backup, then test the upgrade on a staging or other non-production instance before upgrading production.

Questions

When does n8n 1.x support end?

On December 31, 2026, according to n8n. After that date, 1.x is no longer supported.

Can I upgrade from n8n 1.x directly to 3.0?

No. n8n says there is no direct path from 1.x to 3.x: upgrade to 2.x first.

Do I have to move to n8n 3.0 right away?

No. After 3.0 becomes stable, n8n keeps shipping security and critical fixes for 2.x for 12 months. New features only ship on 3.x.

What happens to workflows that use the Function or Cron node?

Those nodes are removed in 3.0. n8n says workflows that use a removed node fail when they run, and published ones do not activate, so their triggers stop firing. Replace Function with the Code node and Cron with the Schedule Trigger node.

Can I roll back from n8n 3.0?

Not directly. n8n says going back to 2.x means restoring a full backup taken before the upgrade.

Every fact on this page is re-read word for word on the vendor’s official page several times a day. Last confirmed: 2026-11-08 04:42 UTC. Sources: n8n blog: Introducing n8n 3.0 (27 October 2026) · n8n Help Center: How do I prepare for n8n 3.0? · n8n docs: v3.0 Breaking changes

A trigger that stops firing does not raise an error by itself. Datvero can alert you when an expected signal from a workflow goes missing.

Monitor your own workflows with Datvero

Datvero is not affiliated with n8n or Zapier. Dates and instructions are the ones the vendors publish.