When is n8n 3.0 released?
n8n's breaking-change page says version 3.0 is "scheduled for October 2026". It does not give a day. When we read that page on October 5, 2026, it did not show a fixed date either. Plan for October, and confirm the date in n8n's release notes before you schedule any change.
The primary source is n8n's page n8n 3.0 breaking changes. This article summarises it and adds what it means for a team that runs workflows. Read the original before you change anything.
Which n8n nodes are removed in 3.0?
The list is longer than most people expect. n8n's page names these nodes as removed: Function, Function Item, Item Lists, LangChain Code (legacy), Cron, Interval, HTML Extract, iCalendar, Convert to/from binary data, Read Binary File, Read Binary Files, Write Binary File, Read PDF, Workflow Trigger, Orbit, OpenAI (legacy version only), OpenAI Assistant, OpenAI Model, HTTP Request Tool (legacy), SerpApi (Google Search), Manual Chat Trigger, Chat Messages Retriever, Motorhead and Zep memory, Binary Input Loader, JSON Input Loader, GitHub Document Loader, several vector store insert and load nodes, Zep Vector Store, and AI Transform.
It also removes the deprecated $getPairedItem expression helper.
| Group | Nodes removed | Who is likely to notice |
|---|---|---|
| Code and logic | Function, Function Item, Item Lists, LangChain Code (legacy), Cron, Interval | Anyone with custom JavaScript or scheduled runs |
| Files and PDFs | Read Binary File, Read Binary Files, Write Binary File, Read PDF, Convert to/from binary data | Document intake and invoice flows |
| Triggers | Workflow Trigger, Manual Chat Trigger | Sub-workflows and chat tests |
| OpenAI and AI | OpenAI (legacy), OpenAI Assistant, OpenAI Model, HTTP Request Tool (legacy), Chat Messages Retriever, AI Transform | Any flow built on older AI nodes |
| Memory and vector stores | Motorhead, Zep memory, Pinecone, Supabase and in-memory vector insert and load, Zep Vector Store | Agents with saved memory or a knowledge base |
| Data sources | SerpApi (Google Search), Binary Input Loader, JSON Input Loader, GitHub Document Loader, Orbit, iCalendar | Research flows and calendar syncs |
The page names replacements for some of these. Its migration notes point to a Code node for Function nodes and a Schedule Trigger for Cron and Interval. For the rest, follow the migration notes on the same page for each node. Do not guess a replacement, because a node that runs without error can still return different data.
How do I find the workflows that use removed nodes?
Search your workflows by node name before the upgrade. In n8n Cloud and self-hosted editors, you can open each workflow and look for the node type, but for a team with dozens of workflows it is faster to export them and search the JSON for the node type names.
Update, October 12, 2026: from n8n 2.43 the migration report in Settings does this for you, sorting affected workflows by impact (Upgrade blocked, Executions fail, Behavior changes, Capability removed). See what is new in n8n 2.43.
A workflow that uses a removed node will not run after the upgrade, and that failure is not always loud. A schedule that stops firing is the one most teams miss, because nothing shows red on screen. Export your schedules and check each one by hand after the change.
Does 3.0 change self-hosted n8n?
Yes. The changelog says self-hosted n8n will require a Docker-based deployment, and that n8n 3.0 will no longer support installs run with npm or npx. If your team starts n8n with a plain npm or npx command, move to Docker in a test environment before you upgrade.
Cloud users are not affected by this part. For them the work is the removed nodes and the defaults below.
Which n8n defaults change in 3.0?
Several environment defaults get stricter. The table lists them as the changelog gives them, with the old and new values.
| Setting | Old default | New default in 3.0 |
|---|---|---|
| N8N_UNVERIFIED_PACKAGES_ENABLED | true | false |
| N8N_RUNNERS_TASK_TIMEOUT | 300 seconds | 60 seconds |
| N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES | 2 GiB | 256 MiB |
| N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES | 5,000 | 1,000 |
| Webflow OAuth2 Legacy toggle | On | Off |
The two that will hit most teams are the unverified packages switch and the one-minute task timeout. If a community node is part of a live flow, turn the package setting on deliberately and record why. If a Code step or sub-workflow runs longer than a minute, split it into batches before the upgrade. The compression limits matter for flows that unzip large files, such as a batch of uploaded documents.
What should an automation team do before the upgrade?
- Inventory. Export every workflow and list the removed node types each one uses. Keep the list in a shared sheet, with an owner for each row.
- Replace one workflow at a time. Use the migration notes for each node. Change the trigger first, then the logic.
- Test on a copy. Run each changed workflow with test credentials that cannot send messages to real customers. Compare the output with the old run.
- Time the long jobs. Anything that takes close to a minute needs to be split.
- Check your environment variables against the table above, and set any value you want to keep explicitly.
- Move self-hosted installs to Docker in a test environment first.
- Upgrade last, with a copy of the database and the workflow files kept for rollback.
Why does this matter for sales and lead workflows?
Lead flows are usually a trigger, a few conditions and a few actions. The risk sits in the timed and file-based steps: a nightly lead recycle, a follow-up that waits two days, a reminder sent before an appointment, or a PDF quote read from an email. Those steps often use Cron, Interval, Read PDF or the binary file nodes, so check them first.
If a flow sends texts or calls, the timing rules are not only technical. A reminder that fires at the wrong hour can break consent rules. Read our note on the FCC opt-out changes before you change any timed step that messages a customer. Our n8n automation services page describes how we set up and test these flows.
Does 3.0 affect n8n Agents?
The n8n Agents feature is separate from the removals. It launched in September 2026. Several of the removed AI nodes, such as the OpenAI Assistant and Model nodes, are older building blocks, so a flow that uses them needs a new home before the upgrade. Read our n8n Agents launch note for what the new feature covers and why it is still in preview.
Frequently asked questions
Will my workflows stop working when 3.0 is released?
Upgrading is your decision. A workflow that uses a removed node will fail after the upgrade, so replace those nodes before you upgrade.
Do I need Docker on n8n Cloud?
No. The Docker requirement applies to self-hosted installs. Cloud users handle the node changes and the defaults.
Which removed node is most likely to break a flow?
The timed and file nodes. Cron and Interval stop schedules, and the binary and PDF nodes stop document intake. Both can fail without an obvious error, so test them first.
Is there a fixed date for 3.0?
Not on the page we read. It says October 2026. Confirm the date in the release notes before you schedule an upgrade.
This article reflects n8n's breaking-change page as read on October 5, 2026. The original page is the final word on the node list and the defaults. If you want help with the inventory and the test copies, contact us, or see our AI workflow automation service.
