The Automation Pulse
Tool We're WatchingNovember 5, 2026

n8n 3.0

By Nuevexa·

Workflow Automation

n8n 3.0 entered beta on October 27, 2026, with stable due in early December. Self-hosting becomes Docker only, legacy nodes are removed, security defaults tighten, and the upgrade is one way. 1.x support ends December 31.

Beta now, stable in December

What changed

n8n released version 3.0.0 in beta on October 27, 2026, with the stable release following in early December. Like 2.0, it is a hardening release: the headline changes remove old paths and tighten defaults rather than add features.

Self-hosted n8n now runs on Docker. Installing with npm or npx is no longer supported. Several legacy nodes are removed, including Function, Function Item, Item Lists, Cron, Interval, and the legacy OpenAI node, along with the first-generation AI Agent. Security defaults are stricter, and the breaking changes list covers the details.

Why it matters in production

Three changes will catch teams out. First, published workflows that still use a removed node stop activating after the upgrade. Second, the default Code node timeout drops from 5 minutes to 1 minute, which affects long-running scripts (it is configurable). Third, the move is one way: there is no going back to 2.x once you upgrade.

The support timeline sets the pace. After 3.0 goes stable, 2.x receives security and critical bug fixes for 12 months. Support for 1.x ends December 31, 2026, and 1.x instances need to step through 2.x on the way to 3.x.

What to do now

If you are on 1.x, plan the move to 2.x this quarter. If you are on 2.x, run the migration report to find workflows that use removed nodes, replace Function and Cron nodes with Code and Schedule nodes, check any Code node that runs longer than a minute, and confirm your hosting runs n8n in Docker. Test 3.0 on a copy of production before the stable release, not after.

Nuevexa is an n8n agency that builds, hosts, and upgrades production n8n deployments, including 1.x and 2.x migrations.

Quarterly intelligence on what's moving in automation

For operators, not just observers.