n8n 3.0 beta is out: what changes before the stable release in December

n8n released the 3.0.0 beta on 27 October 2026, with the stable 3.x release planned for early December. Version 3.0 focuses on reliability and security: self-hosted n8n now runs on Docker only, several old nodes are removed, security defaults are stricter, and there is no rollback to 2.x except from a backup. A Migration Report in n8n 2.39 and later shows which workflows need changes.

What changes in n8n 3.0

Self-hosting - Self-hosted n8n runs on Docker. Installing with npm or npx is no longer supported; n8n offers a one-line setup script instead. - Kubernetes and Helm deployments are not affected.

Removed nodes and features - Function and Function Item are removed: use the Code node. - Item Lists is removed: use Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize. - Cron and Interval are removed: use the Schedule Trigger. - The legacy OpenAI node, older AI Agent modes, older Edit Image versions and nodes for discontinued services are removed. - Import from URL is removed from the editor, and Chat Hub is off by default.

Reliability and security - In queue mode, manual executions run on workers rather than the main instance. - The in-memory binary data mode is removed: binary data goes to the filesystem or external storage such as S3. - The default Code node timeout drops from 5 minutes to 1 minute, and it can be changed. - Encryption key rotation is always on, Slack credentials need a signing secret, and unverified community packages are off by default.

Who is affected

Every edition gets 3.0: Community, Cloud, Business and Enterprise. Credentials and execution history carry over. If you are still on 1.x, you must upgrade to 2.x first, because there is no direct path to 3.x, and 1.x support ends on 31 December 2026. After the stable release, 2.x receives security and critical bug fixes for 12 months.

How to upgrade safely

1. Update to the latest 2.x and open Settings, then Migration Report. It needs version 2.39 or later. 2. Fix or mark "won't fix" every workflow and setting it flags. Many issues are fixed automatically as new workflow versions for you to review. 3. Take a full backup. There is no downgrade from 3.x. 4. Upgrade a test copy first, run your important workflows, then upgrade production. 5. Self-hosting with npm? Move to Docker before you upgrade.

What it means for businesses

If your business runs on n8n workflows, December is the deadline to plan for, not the day to discover a Function node in a payroll or invoicing flow. Run the Migration Report this week, list the workflows that matter, and test them on a copy. Our business process automation team builds and maintains n8n, Make and Zapier workflows and can run the upgrade for you, and our Zapier vs Make vs n8n comparison covers which tool fits which job.