n8n releases 3.0 beta with changes that may affect workflows
By Automate Basics, written with AI from n8n's original
n8n has released a 3.0 beta that changes older workflow components, security defaults and self-hosting requirements. People who run automations can use a Migration Report to see what needs attention before the stable release.
The short version
- What happened: n8n released a 3.0 beta with breaking changes that may require workflow or settings updates.
- Who gets it: Cloud and self-hosted users can try the beta; n8n has not said whether pricing changes.
- What to do: Update to the latest 2.x release, then check Settings > Migration Report before upgrading.
What changed in AI this week, and how to use it at work, by email on Mondays.
What changed in n8n 3.0?
n8n says the n8n 3.0 beta is available now, with a stable release planned for early December. The update concentrates on reliability and security rather than a new set of features. It also removes older components, so some workflows and instance settings may need changes before an upgrade.
The old Cron and Interval nodes give way to Schedule Trigger. Other retired nodes include Function, Function Item, Item Lists and the legacy OpenAI node. n8n says many affected workflows can migrate automatically, but owners should review the result. Security changes include safer defaults for encryption key rotation and unverified community packages. Moving to 3.x is one way: returning to 2.x requires restoring a backup.
Who can use the n8n 3.0 beta?
n8n 3.0 applies to Cloud, self-hosted Community, and Enterprise and Business editions. Cloud users can select the beta when changing their n8n version. Self-hosted users can install it as a beta release. n8n has not said whether 3.0 changes pricing.
The upgrade has a particular consequence for people who manage their own installation: n8n no longer supports installing with npm or npx. Self-hosted installations now run on Docker, while Kubernetes and Helm deployments are unaffected. People still on 1.x must move to 2.x before upgrading to 3.x. After the stable release, n8n says 2.x will receive security and critical bug fixes for 12 months, but new features will arrive on 3.x.
What should I do before upgrading?
n8n recommends updating to the latest 2.x release and opening Settings > Migration Report. The report is available on instances running version 2.39 or later. It identifies affected workflows and instance settings, and can fix many issues automatically. Each automatic fix becomes a new workflow version to review and publish; existing published workflows continue running on 2.x while that work happens.
For a team that relies on scheduled work, the report is a way to check whether an older node needs replacing before the upgrade interrupts the routine. Review what it flags, fix the items you need, and mark irrelevant ones “won’t fix.” n8n advises upgrading a test or staging instance before production and taking a full backup, because an upgrade to 3.x cannot simply be reversed.
Frequently asked questions
Will n8n 3.0 change my existing workflows?
Some workflows may need changes because n8n 3.0 removes older nodes and changes some settings. On version 2.39 or later, Settings > Migration Report identifies affected workflows. n8n says it can fix many issues automatically, but you should review and publish the resulting workflow versions.
Can I return to n8n 2.x after trying 3.0?
No. n8n says moving to 3.x is one way, and returning to 2.x means restoring a full backup. It recommends trying the beta on a test instance first and backing up your installation before upgrading.
For you
Learn to do this with AI, free
Short courses for people who aren't engineers: ChatGPT, Claude, prompting and automation. Every lesson is free, with no card.
Start a free courseFor companies
Make an AI or automation tool?
List it in the directory for $9.99, refunded in full if it isn't approved, or claim its page if it is already here.
Related reading
n8n explains how to check AI agent answers before workflows continuen8n has published guidance on checking AI agent answers before they trigger later workflow steps. It describes how teams can combine answer checks, trusted sources and human review in n8n.
n8n shows how to run AI invoice workflows on an office computern8n has published a guide to running its AI workflows on an office-based NVIDIA DGX Spark rather than calling a cloud model API. The setup is aimed at teams that need to keep documents and recordings under their control.
n8n adds Gemini 4 Argon to agents and workflow-building optionsn8n says users can choose Gemini 4 Argon for agents and its Google Gemini node. They can also build workflows with the model through an MCP-connected tool or, on self-hosted instances, connect it to the n8n Assistant through another provider route.
Tools in this piece
Written with AI from n8n's original and published after automatic checks: every figure here appears in the original, and no sentence is copied from it. The picture is AI-generated. The original is the authority.
Get the next one by email
One email a week: what changed in AI for people who use it at work, and what to do about it.
Source: Introducing n8n 3.0, n8n, 27 Oct 2026.