n8n 3.0 is in beta: what to check before you upgrade

n8n released the beta of version 3.0 on 27 October 2026. The stable release is planned for early December. After that, the 2.x line keeps receiving security and critical fixes for twelve months, but new features ship only on 3.x. Support for 1.x ends on 31 December 2026, and there is no direct path from 1.x to 3.0: you go through 2.x first.

What changes

This is a major version, and n8n says some workflows and settings will need updating. The changes that matter most for the systems we run:

• Old nodes are removed. Function and Function Item give way to the Code node. Item Lists is replaced by Split Out, Aggregate, Sort, Limit, Remove Duplicates and Summarize. Cron and Interval are replaced by the Schedule Trigger. The legacy OpenAI node and older AI Agent modes also go.
• Self-hosting means Docker. Installing with npm or running npx n8n is no longer supported. Kubernetes and Helm deployments are unaffected.
• Tighter defaults. Encryption key rotation is always on, Slack credentials need a signing secret and unverified community packages are off by default.
• Shorter timeouts. The Code node’s default task runner timeout drops from five minutes to one, so long-running code steps need a look.

How to prepare

n8n has added a migration report to recent 2.x versions (2.39 and later), under Settings. It lists the workflows and settings 3.0 will affect, offers automatic fixes saved as new workflow versions and can be exported.

The order we follow for client instances:

1. Update to the latest 2.x and run the migration report.
2. Fix or consciously accept every flagged item.
3. Take a full backup. The upgrade can’t be rolled back without one.
4. Upgrade a staging copy first and run the important workflows end to end.
5. Upgrade production in a quiet window. n8n says it needs only a short restart, and credentials and execution history carry over.

What it means for you

If we built or run an n8n instance for you, nothing changes until the stable release, and we’ll plan the upgrade with you before then. If you self-host n8n with npm, that is the change to plan for first.

Source: Introducing n8n 3.0, n8n blog, 27 October 2026.