n8n 3.0 Is Coming: Breaking Changes and How to Prepare (2026)

If you run n8n, the automation platform a lot of freelancers and small teams have adopted as the cheaper, self-hostable alternative to Zapier, there is a major version on the way that deserves your attention. n8n 3.0 is scheduled for October 2026, and n8n’s own documentation describes it as a security and cleanup-focused release: tighter defaults, a Docker-only deployment model for self-hosters, and the removal of nodes and helpers that newer patterns replaced years ago.

The good news: most recently built workflows will not notice a thing. The less good news: if you self-host with npm, still use the old Function node, or built AI agents on the version 1 AI Agent node, you have work to do before you upgrade.

This guide walks through every confirmed breaking change, who it affects, and a practical checklist to get ready. Everything below comes from n8n’s official v3.0 breaking-changes documentation, which n8n says it will keep updating as the release approaches.

The short answer: n8n 3.0 is a cleanup release, not a feature release. The three changes that matter most: (1) self-hosted installs must run on Docker, npm and npx installs stop being supported; (2) a long list of legacy nodes is removed, including Function, Cron, and Interval; (3) the Code node task timeout drops from 5 minutes to 1 minute. Run the Migration Report under Settings before you upgrade, it tells you exactly which of your workflows are affected. If you are still choosing a platform, our n8n vs Zapier comparison and Make vs n8n breakdown cover the wider decision.

When Is n8n 3.0 Coming Out?

n8n’s documentation says 3.0 is “releasing soon,” with the release window widely reported as October 2026. The 2.x line is still getting releases in the meantime, so nobody is forced to jump on day one. n8n recommends the Stable release track for anything important, pinning an exact version, and updating monthly so the jumps stay small.

One honest caveat from the people who have read the docs closely: n8n’s breaking-changes page itself says it will be updated “with full details, migration guides, and links as n8n 3.0 approaches its release.” A few items are still vague in the source document. Where that is true, this guide says so instead of inventing detail.

Change 1: Self-Hosted n8n Becomes Docker-Only

This is the headline change. n8n 3.0 no longer supports installations run with npm or npx n8n, and it does not publish a runnable n8n package to npm at all.

What this means in practice:

• If you installed n8n with npm install -g n8n or run it via npx n8n, that setup stops working with 3.0.
• If you run n8n under pm2 or another process manager without Docker, same story.
• If you already run n8n in Docker or with Docker Compose, nothing changes for you.

What to do: move to a Docker-based deployment before upgrading. n8n’s fastest path is its one-line setup, which checks Docker, writes the configuration files, and starts a fresh instance with a single command. For a team or production instance, Docker Compose with PostgreSQL is the recommended setup. Export your workflows and credentials from the old instance first, then import them into the new one. If you already run your own Docker Compose file, you do not need to switch.

Change 2: Legacy Nodes Are Removed

This is the longest list in the release. n8n 3.0 removes older nodes that newer patterns replaced. Workflows that use a removed node will fail, so this is the change most likely to break a working setup.

The removals that matter most to freelancers and small teams:

The Function-to-Code migration deserves a callout because the Function node was the workhorse of early n8n workflows. The Code node does everything the Function node did, and the migration is mostly mechanical: open each Function node, copy the logic, paste it into a Code node in the matching run mode. The Migration Report flags every affected workflow, so you do not have to hunt them down by hand.

Change 3: AI Agent v1 Modes Are Retired

Version 1 of the AI Agent node supported several agent type modes, including SQL Agent, Conversational Agent, OpenAI Functions Agent, Plan and Execute Agent, and ReAct Agent. n8n 3.0 removes version 1 of the node along with these modes.

The replacement is the Tools Agent, which is what the current AI Agent node uses. Workflows already set to Tools Agent keep working the same after you update. If you built agents on one of the old modes, update those workflows to the latest AI Agent version before upgrading. For SQL Agent use cases specifically, n8n recommends a Postgres or MySQL tool sub-node paired with a recent AI Agent node.

Change 4: Code Node Timeout Drops to One Minute

The default task runner timeout drops from 300 seconds (5 minutes) to 60 seconds (1 minute). Code node tasks that run longer than a minute will fail after the upgrade.

This catches people who use the Code node for heavy lifting: large file processing, long API pagination loops, big data transforms. If your Code tasks need more than a minute, set the timeout variable explicitly before upgrading. Better yet, treat the new default as a nudge to break long tasks into smaller steps, which is more reliable anyway.

Change 5: Security Defaults Get Tighter

Several changes make n8n safer out of the box:

• Encryption key rotation is now on by default. You can manage keys under Settings, Data Encryption Keys. Back up your database before upgrading, as with any major version.
• The Slack API credential now requires a signing secret. Workflows with a Slack Trigger node will fail to publish and return 401 errors until you add it. Add the secret before you upgrade, not after.
• The Compression node decompression limits drop from 2 GiB to 256 MiB max decompressed size. If you process large archives, set the old values explicitly before upgrading.
• Unverified community nodes are off by default. Installed unverified nodes stop loading unless you opt back in.
• The deprecated $getPairedItem expression helper is removed. Use standard item linking instead.

Change 6: Chat Hub, Ask AI, and Other Retirements

• Chat Hub is turned off by default in 3.0, and removed entirely in n8n 4.0. If you rely on it, add chat-hub to the N8N_ENABLED_MODULES environment variable to keep it through the 3.x line.
• The Ask AI tab is removed from the Code node. Code you already generated stays in place and keeps running; write new code directly in the Code tab.
• Workflow import from URL is removed from the editor. Use copy-paste, Import from File, the CLI, or the API instead.
• The storage directory is renamed from ~/.n8n/binaryData to ~/.n8n/storage. If you mount a volume at the old path, update it before upgrading.

Who Is Affected, and Who Can Relax?

• n8n Cloud users: mostly unaffected. n8n handles the infrastructure, so your job is checking workflows for removed nodes via the Migration Report.
• Docker self-hosters with modern workflows: light touch. Run the Migration Report and fix what it flags.
• npm, npx, or pm2 self-hosters: this is your migration project. Move to Docker first, confirm everything runs on 2.x in the container, then upgrade.
• Anyone with old Function, Cron, or Interval nodes, or AI Agent v1: budget time for the node migrations in the table above.

Your n8n 3.0 Migration Checklist

• Back up everything. Export workflows and credentials, and take a database dump.
• Open Settings, Migration Report on your current instance. It lists every workflow and setting that 3.0 will break.
• If you self-host without Docker, migrate to Docker first and confirm everything runs on 2.x in the container.
• Replace removed nodes using the table above, starting with Function, Cron, and Interval.
• Update AI Agent v1 workflows to the Tools Agent.
• Check Code node runtimes. Set the timeout variable explicitly if anything needs more than 60 seconds.
• Add the Slack signing secret if you use Slack Trigger nodes.
• Upgrade a test instance first if you run anything business-critical.
• Upgrade production, then verify your key workflows run.

n8n 3.0 FAQs

When is n8n 3.0 being released?

n8n’s official documentation says 3.0 is “releasing soon,” with the release window widely reported as October 2026. The 2.x line continues to receive updates in the meantime, so there is no need to rush. Pin your current version and plan the migration on your own schedule.

Will my existing workflows break when I upgrade to n8n 3.0?

Only if they use something 3.0 removes. Workflows built with current nodes are fine. The reliable way to know is the Migration Report under Settings, which scans your instance and lists every affected workflow before you upgrade. Run it before you touch anything.

Do I really need Docker to run n8n now?

For self-hosting, yes. n8n 3.0 requires a Docker-based deployment and no longer supports npm or npx installs. n8n Cloud users are unaffected. If the word Docker worries you, n8n’s one-line setup handles the whole thing with a single command.

What replaces the Function node in n8n 3.0?

The Code node. Use “Run Once for All Items” mode where you used Function, and “Run Once for Each Item” where you used Function Item. The migration is mostly copy-paste, and the Migration Report finds every Function node for you.

What happened to the AI Agent node in n8n 3.0?

Version 1 of the AI Agent node is removed, including its SQL Agent, Conversational Agent, OpenAI Functions Agent, Plan and Execute, and ReAct modes. The current Tools Agent replaces all of them. Update AI Agent v1 workflows to the latest node version before upgrading.

Should I upgrade to n8n 3.0 right away?

Not on day one for anything business-critical. Let the early adopters find the sharp edges, keep an eye on the release notes, and upgrade once the first patch releases land. Use the waiting time to run the Migration Report and clear its findings.