> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/changelog/v30-breaking-changes.md).
# v3.0 Breaking changes
Breaking changes coming in n8n 3.0
n8n 3.0 has been released, and with it came some important changes. This document highlights breaking changes and actions you should take to prepare for the transition. These updates improve security, simplify configuration, and remove legacy features.
Before you upgrade, open the Migration Report at **Settings > Migration Report**. It lists the workflows and instance settings on your own instance that need attention, so you don't have to check every change on this page by hand.
## Deployment
### Docker-based deployment required for self-hosted n8n
Self-hosted n8n requires a Docker-based deployment. n8n 3.0 no longer supports installations run using `npm` or `npx n8n`, and n8n 3.0 doesn't publish a runnable `n8n` package to npm.
**What to do:** If you run n8n with [npm](/deploy/host-n8n/install-options/install-with-npm.md) or `npx n8n`, move to a Docker-based deployment before you upgrade to n8n 3.0. The fastest path is the [one-line setup](/deploy/host-n8n/install-options/one-line-setup.md), which checks Docker, writes the configuration files, and starts a new n8n instance with a single command:
```bash
curl -fsSL https://get.n8n.io | sh
```
If you already run your own Docker Compose file, you don't need to switch. For a team or production instance, [Install using Docker Compose](/deploy/host-n8n/install-options/install-using-docker-compose.md) covers running n8n with Postgres instead of the bundled SQLite database.
## Community node development
### `defaults.color` removed from the node description
n8n 3.0 removes the deprecated `defaults.color` property from the node description type. It only tinted Font Awesome icons (`icon: 'fa:...'`). Community nodes that still set it keep working, but the editor shows a Font Awesome icon in a neutral color. Nodes with a file icon (`icon: 'file:...'`) aren't affected, because n8n never tints file icons.
**What to do:** Remove `defaults.color`. If your node uses a Font Awesome icon, replace it with an SVG or PNG file icon, as the [standard parameters](/connect/create-nodes/build-your-node/reference/base-files/standard-parameters.md#icon) reference recommends.
The remaining changes affect the [`n8n-node dev`](/connect/create-nodes/build-your-node/using-the-n8n-node-tool.md) test loop only. `n8n-node build`, `n8n-node lint`, `n8n-node release`, and `npm create @n8n/node` are unchanged.
### n8n-node dev requires Docker or Podman
`n8n-node dev` started n8n with `npx n8n@latest`. n8n 3.0 doesn't publish a runnable `n8n` package to npm, so the command now runs the official image in a container.
**What to do:** For the default container path, install Docker or Podman. To use an externally managed instance instead, run `n8n-node dev --external-n8n` and start that instance with `N8N_DEV_RELOAD=true`. To pin a version on the container path, pass the tag: `n8n-node dev --n8n-image docker.n8n.io/n8nio/n8n:`. Hot reload only works on images that serve `POST /rest/dev/reload`, so older tags load your node but need a restart to pick up changes.
### n8n-node dev test data moves to a per-image container volume
Workflows and credentials you create while testing your node now live in a `n8n-node-cli-data-` container volume, not in `~/.n8n-node-cli/.n8n`. Each `--n8n-image` gets its own volume, because n8n only migrates a database forward. Switching images gives you an empty instance rather than a database an older n8n version can't read.
{% hint style="warning" %}
**Test data from earlier versions doesn't carry over**
Export any test workflows you want to keep before you upgrade the CLI or change images.
{% endhint %}
**What to do:** Export the test workflows you want to keep. To list and reset the volumes, use `docker volume ls --filter name=n8n-node-cli-data` and `docker volume rm `, or the `podman` equivalents.
### `--custom-user-folder` only applies with `--external-n8n`
The flag used to set where the CLI linked your node. It now names the `N8N_USER_FOLDER` of the instance you run yourself and has no effect in container mode.
**What to do:** If you pass `--custom-user-folder`, add `--external-n8n` and start that instance with the same `N8N_USER_FOLDER`.
## Removed nodes and helpers
n8n 3.0 removes older nodes, modes, and helpers that newer patterns have replaced.
### Removed nodes
Workflows that use a removed node fail. Before you upgrade, **Settings > Migration Report** lists the affected workflows on your instance, and the [Deprecated and versioned nodes](/integrations/builtin/deprecated-nodes.md) page tracks the final version of every node listed here.
* **Function** node (legacy)
* **Function Item** node (legacy)
* **Item Lists** node (legacy)
* **LangChain Code** node (legacy)
* **Cron** and **Interval** nodes
* **HTML Extract** node
* **iCalendar** node
* **Convert to/from binary data** node
* **Read Binary File**, **Read Binary Files**, and **Write Binary File** nodes
* **Read PDF** node
* **Workflow Trigger** node
* **Orbit** node
* **OpenAI** node (legacy). The current **OpenAI** node in the AI section stays.
* **OpenAI Assistant** and **OpenAI Model** nodes
* **HTTP Request Tool** node (legacy). Using the **HTTP Request** node as a tool stays.
* **SerpApi (Google Search)** node
* **Manual Chat Trigger** node
* **Chat Messages Retriever** node
* **Motorhead** and **Zep** memory nodes
* **Binary Input Loader**, **JSON Input Loader**, and **GitHub Document Loader** nodes
* **In Memory Vector Store Insert**, **In Memory Vector Store Load**, **Pinecone: Insert**, **Pinecone: Load**, **Supabase: Insert**, **Supabase: Load**, **Zep Vector Store**, **Zep Vector Store: Insert**, and **Zep Vector Store: Load** nodes
* **AI Transform** node: n8n automatically migrates existing nodes to [Code](/integrations/builtin/core-nodes/n8n-nodes-base.code.md) nodes on upgrade, keeping the same generated JavaScript, so existing workflows keep working without changes. You can no longer add an **AI Transform** node. Write JavaScript directly in the **Code** node instead.
* **What to do:** Migrate affected workflows to the current recommended alternatives before upgrading:
* Replace **Function** and **Function Item** nodes with the [Code](/integrations/builtin/core-nodes/n8n-nodes-base.code.md) node. Use **Run Once for All Items** mode in place of **Function**, and **Run Once for Each Item** mode in place of **Function Item**.
* Replace the **Item Lists** node with the node matching the operation you use: [Split Out](/integrations/builtin/core-nodes/n8n-nodes-base.splitout.md), [Aggregate](/integrations/builtin/core-nodes/n8n-nodes-base.aggregate.md), [Sort](/integrations/builtin/core-nodes/n8n-nodes-base.sort.md), [Limit](/integrations/builtin/core-nodes/n8n-nodes-base.limit.md), [Remove Duplicates](/integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates.md), or [Summarize](/integrations/builtin/core-nodes/n8n-nodes-base.summarize.md).
* Replace **Cron** and **Interval** with the [Schedule Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger.md) node.
* Replace **HTML Extract** with the [HTML](/integrations/builtin/core-nodes/n8n-nodes-base.html.md) node's **Extract HTML Content** operation.
* Replace **iCalendar** with the [Convert to File](/integrations/builtin/core-nodes/n8n-nodes-base.converttofile.md) node's **Convert to ICS** operation.
* Replace **Convert to/from binary data** with the [Convert to File](/integrations/builtin/core-nodes/n8n-nodes-base.converttofile.md) or [Extract from File](/integrations/builtin/core-nodes/n8n-nodes-base.extractfromfile.md) node.
* Replace **Read Binary File**, **Read Binary Files**, and **Write Binary File** with the [Read/Write Files from Disk](/integrations/builtin/core-nodes/n8n-nodes-base.readwritefile.md) node.
* Replace **Read PDF** with the [Extract from File](/integrations/builtin/core-nodes/n8n-nodes-base.extractfromfile.md) node's **Extract From PDF** operation.
* Replace **Workflow Trigger** with the [n8n Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.n8ntrigger.md) node.
* Replace the legacy **OpenAI** node and the **OpenAI Assistant** node with the [OpenAI](/integrations/builtin/app-nodes/n8n-nodes-langchain.openai.md) node. For assistants, use its **Assistant** resource.
* Replace **OpenAI Model** with the [OpenAI Chat Model](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmchatopenai.md) node.
* Replace the legacy **HTTP Request Tool** with the **HTTP Request** node connected to the **Tool** input of the **AI Agent** node.
* Replace **Manual Chat Trigger** with the [Chat Trigger](/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger.md) node.
* Replace **Chat Messages Retriever** with the [Chat Memory Manager](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymanager.md) node, or load previous sessions in the **Chat Trigger** node.
* Replace **Binary Input Loader**, **JSON Input Loader**, and **GitHub Document Loader** with the [Default Data Loader](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.documentdefaultdataloader.md) node. For GitHub content, fetch it with the **GitHub** node first.
* Replace the **Insert** and **Load** vector store nodes with the single node for that store: [Simple Vector Store](/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.vectorstoreinmemory.md), [Pinecone Vector Store](/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.vectorstorepinecone.md), or [Supabase Vector Store](/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.vectorstoresupabase.md). Pick the operation (**Insert Documents**, **Get Many**, or **Retrieve Documents**) in the node.
* [**LangChain Code**](/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.code.md) has no direct replacement.
* **Motorhead**, **Zep**, and the **Zep Vector Store** nodes have no direct replacement. Use another supported [memory](/integrations/builtin/cluster-nodes/sub-nodes.md) or [vector store](/integrations/builtin/cluster-nodes/root-nodes.md) node.
* **SerpApi (Google Search)** has no direct replacement. Call the SerpApi REST API with the **HTTP Request** node connected as a tool, or use a verified [community node](/integrations/community-nodes/installation-and-management.md).
* **Orbit** has no replacement. The Orbit service shut down.
### Removed expression helpers
n8n 3.0 removes the deprecated `$getPairedItem` expression helper. Expressions that still call it fail when the node runs.
**What to do:** Use n8n's standard [item linking](/build/work-with-data/reference-data/link-data-items/how-items-link-through-workflows.md) instead. Three forms replace `$getPairedItem`:
* `$('').item` returns the item in `` that the current item links back to.
* `$('').itemMatching()` returns the item in `` that the input item at `` links back to.
* `$('').pairedItem()` returns the paired item for `` directly.
### Execute Sub-workflow node: Local File and URL sources removed
n8n 3.0 removes the **Local File** and **URL** options from the **Source** parameter of the [Execute Sub-workflow](/integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow.md) node. Only node versions 1.1 and older offered them. Nodes that still use one of these sources fail with an error.
**What to do:** Import the sub-workflow into your instance and select it with the **Database** source, or paste its JSON with the **Define Below** source (**Parameter** on node versions 1.1 and older). Before you upgrade, go to **Settings > Migration Report** to identify the affected nodes.
### `$evaluateExpression()` removed from the Code node
n8n 3.0 removes the `$evaluateExpression()` convenience method from the [Code](/integrations/builtin/core-nodes/n8n-nodes-base.code.md) node (JavaScript). Only [task runners](/deploy/host-n8n/configure-n8n/set-up-task-runners.md) in insecure mode (`N8N_RUNNERS_INSECURE_MODE=true`) are affected. Secure-mode runners, the default since n8n 2.0, already fail on this call.
**What to do:** Evaluate the expression in a node field instead, for example in an [Edit Fields (Set)](/integrations/builtin/core-nodes/n8n-nodes-base.set.md) node before the **Code** node, and read the result from the input item. `$evaluateExpression()` continues to work in `{{ }}` expression fields.
### AI Agent node: Older agent modes removed
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.
**What to do:** Update any workflows and templates that use version 1 of the [AI Agent](/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.agent.md) node to the latest version. The latest version replaces all the removed modes with **Tools Agent**, and workflows already set to **Tools Agent** continue to behave the same after you update. For **SQL Agent** use cases, replace it with a [Postgres](/integrations/builtin/app-nodes/n8n-nodes-base.postgres.md) or [MySQL](/integrations/builtin/app-nodes/n8n-nodes-base.mysql.md) tool sub-node paired with a recent **AI Agent** node.
## Behavior changes
n8n 3.0 changes how some nodes and credentials behave. These nodes stay available, but existing workflows can produce different results.
### Always Output Data on nodes with several outputs
With [**Always Output Data**](/build/understand-workflows/workflow-components/work-with-nodes.md) on, nodes with multiple outputs, for example [If](/integrations/builtin/core-nodes/n8n-nodes-base.if.md) and [Switch](/integrations/builtin/core-nodes/n8n-nodes-base.switch.md), now add an empty item only when every output is empty. Previously, each empty output got an empty item, so branches ran when they shouldn't have.
**What to do:** Before you upgrade, go to **Settings > Migration Report** to identify the nodes this change affects. Review each node and adjust the setting to match your intent.
### Gmail Trigger node: Older versions run as version 1.4
n8n 3.0 removes the separate behavior of **Gmail Trigger** node versions 1 to 1.3. Workflows that use these versions keep loading, but the node runs with the version 1.4 behavior:
* **Max Emails per Poll** applies to every poll. The default is 10 emails, and you can set up to 50. The node picks up the remaining emails in later polls.
* The node skips drafts unless you turn on the **Include Drafts** filter. Versions 1 and 1.1 included drafts by default.
* Sent emails that aren't in the inbox, and scheduled emails, no longer trigger the workflow.
**What to do:** Review workflows with a **Gmail Trigger** node below version 1.4. Before you upgrade, go to **Settings > Migration Report** to identify the affected nodes. If a workflow relies on drafts, turn on **Include Drafts**. If a workflow relies on sent or scheduled emails, replace the trigger with a [Schedule Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger.md) node followed by the [Gmail](/integrations/builtin/app-nodes/n8n-nodes-base.gmail.md) node's **Get Many** messages operation.
### Webflow OAuth2 credential: Legacy toggle off by default
The **Legacy** toggle on the [Webflow OAuth2 API](/integrations/builtin/credentials/webflow.md) credential defaults to off. New credentials request the Webflow v2 API scopes (`cms:read cms:write sites:read forms:read`). Existing credentials that never saved an explicit **Legacy** value request these scopes the next time you reconnect them. Connected credentials keep working. n8n doesn't touch stored tokens, and token refresh doesn't send scopes.
**What to do:** If you still use the deprecated Webflow v1 Data API, for example with a legacy Webflow OAuth app or the [Webflow](/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md) node at version 1, turn on **Legacy** on the credential before you reconnect it. Webflow rejects the connection if the requested scopes aren't configured on your app.
### Chat Trigger node: WebSocket messages are JSON frames
The chat WebSocket endpoint that the [Chat Trigger](/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger.md) node uses in the **Using Response Nodes** response mode, where the **Chat** node sends replies, now sends every frame as a JSON object with a `type` field: `heartbeat`, `continue`, `error`, `message`, or `with-buttons`. Before, control frames and plain text replies were raw strings. A text reply is now `{ "type": "message", "text": "..." }`. The client acknowledges heartbeats with `{ "type": "heartbeat-ack" }`, and n8n ignores incoming frames that aren't JSON.
The n8n chat widget (`@n8n/chat`) understands both formats from version 1.31.0, and the hosted chat page always loads a current widget.
**What to do:** If you built a custom chat client that talks to the chat WebSocket directly, parse every frame as JSON and switch on `type`. If you embed `@n8n/chat` yourself, update it to version 1.31.0 or later before you upgrade n8n.
## Security
Security defaults are getting stronger to make n8n safer by default. These changes may affect existing workflows or credentials.
### Encryption key rotation on by default
n8n 3.0 turns on [encryption key rotation](/deploy/host-n8n/configure-n8n/security/rotate-encryption-keys.md) by default. Before, self-hosted instances had to opt in to the feature. With it on, n8n keeps a data encryption key that you can rotate from **Settings > Data Encryption Keys**. Credentials and other data encrypted before the upgrade stay readable, and n8n re-encrypts each record to the current key the next time you update it.
Turning the feature on used to be permanent. From n8n 2.40.3, you can turn it off again.
**What to do:** Nothing. As with any upgrade, back up your database first.
### Slack API credential requires the signing secret
n8n 3.0 requires a signing secret on the **Slack API** credential. The [Slack Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.slacktrigger.md) node verifies incoming requests against it, and version 2 of the node makes the field required.
When you need to act depends on how you use the credential:
* **Workflows with a Slack Trigger node:** Add the secret before you upgrade. Until you do, the workflow fails to publish and the trigger responds with a 401 error.
* **Every other Slack workflow:** Add the secret the next time you edit the credential.
{% hint style="warning" %}
**Add the secret before you upgrade**
Workflows with a **Slack Trigger** node stop receiving events until the **Slack API** credential has a signing secret.
{% endhint %}
**What to do:**
1. In your Slack app settings, open **Basic Information** and copy the **Signing Secret**.
2. Paste it into the **Slack API** [credential](/integrations/builtin/credentials/slack.md) in n8n.
3. Publish the workflow again.
### Larger default SSRF block list
When `N8N_SSRF_PROTECTION_ENABLED` is `true` and `N8N_SSRF_BLOCKED_IP_RANGES` contains `default`, n8n 3.0 adds four ranges to the built-in default list:
| Range | Description |
| --------------- | ---------------------------------------- |
| `::/128` | IPv6 unspecified address |
| `100.64.0.0/10` | Shared address space (carrier-grade NAT) |
| `2002::/16` | 6to4 |
| `64:ff9b::/96` | NAT64 well-known prefix |
Requests to hosts in these ranges fail.
**What to do:** If your workflows call hosts in these ranges, add their IP ranges to `N8N_SSRF_ALLOWED_IP_RANGES`, or their hostnames to `N8N_SSRF_ALLOWED_HOSTNAMES`. Keep `default` in `N8N_SSRF_BLOCKED_IP_RANGES`: it's the keyword for the whole built-in list, including localhost, private networks, and the cloud metadata endpoint. If you replace it with literal ranges, you must list every range from the current built-in list yourself. See [Enable SSRF protection](/deploy/host-n8n/configure-n8n/security/enable-ssrf-protection.md) and the [SSRF protection environment variables](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/ssrf-protection.md).
### Lower Compression node decompression limits
The default `N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES` drops from 2 GiB to 256 MiB, and the default `N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES` drops from 5,000 to 1,000. The [Compression](/integrations/builtin/core-nodes/n8n-nodes-base.compression.md) node fails on archives above either limit.
**What to do:** If your workflows decompress archives larger than 256 MiB or with more than 1,000 entries, set these variables explicitly to their previous values (2147483648 and 5000) before upgrading to n8n 3.0. See the [node environment variables](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/nodes.md) reference.
## Configuration
n8n 3.0 changes some defaults and removes settings that only kept older behavior alive. n8n logs a deprecation warning at startup on 2.x for each of these when your instance is affected.
### Remove N8N\_PRE\_EXECUTE\_ERROR\_CREATES\_EXECUTION
n8n 3.0 removes the `N8N_PRE_EXECUTE_ERROR_CREATES_EXECUTION` environment variable. If a `workflow.preExecute` [external hook](/deploy/host-n8n/configure-n8n/external-hooks.md) throws, n8n never creates an execution record. The run never starts, so it doesn't count toward Insights or license usage. There's no way to keep the old behavior.
**What to do:** If you set `N8N_PRE_EXECUTE_ERROR_CREATES_EXECUTION=true` to still create a failed execution when the hook throws, remove the variable before you upgrade to n8n 3.0. After you upgrade, n8n ignores the variable. If you rely on those failed execution records for alerting, move the alert to the external hook itself. Before you upgrade, **Settings > Migration Report** shows whether this instance sets the variable.
### Storage directory renamed
On first start, n8n 3.0 renames `~/.n8n/binaryData` to `~/.n8n/storage` and removes `N8N_MIGRATE_FS_STORAGE_PATH`.
{% hint style="warning" %}
**n8n won't start if both directories exist**
If `~/.n8n/binaryData` and `~/.n8n/storage` both exist, n8n 3.0 stops with an error instead of guessing which one to use.
{% endhint %}
**What to do:** If you mount a volume at `~/.n8n/binaryData`, mount it at `~/.n8n/storage` instead, or set `N8N_STORAGE_PATH` to the old path to keep it. If both directories exist, move the contents of `~/.n8n/binaryData` into `~/.n8n/storage`, remove `~/.n8n/binaryData`, then start n8n again. Nothing to do if you use the default paths without a volume mount. See [Handle binary data](/deploy/host-n8n/configure-n8n/scaling/handle-binary-data.md).
### In-memory binary data mode removed
`N8N_DEFAULT_BINARY_DATA_MODE=default` is no longer valid. Instances that still use it switch to `filesystem` on upgrade.
**What to do:** Set `N8N_DEFAULT_BINARY_DATA_MODE` to `filesystem`, `s3`, `azure`, or `database`, and check that your container's mounted disk has room for binary data. See the [binary data environment variables](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/binary-data.md) reference.
### Changed defaults and removed variables
* **Unverified community packages off by default.** The default for `N8N_UNVERIFIED_PACKAGES_ENABLED` changes from `true` to `false`. After the upgrade, you can't install unverified community nodes from npm, and installed ones stop loading.
* **What to do:** Set `N8N_UNVERIFIED_PACKAGES_ENABLED=true` to keep installing unverified community nodes from npm, or move to [verified community nodes](/integrations/community-nodes/installation-and-management/install-verified-community-nodes.md).
* **Shorter task runner timeout.** The default for `N8N_RUNNERS_TASK_TIMEOUT` drops from `300` (5 minutes) to `60` (1 minute). Code node tasks that run longer fail.
* **What to do:** Set `N8N_RUNNERS_TASK_TIMEOUT` explicitly if your tasks need more than a minute. See the [task runner environment variables](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/task-runners.md).
* **Manual executions always run on workers in queue mode.** `OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS` is removed.
* **What to do:** Remove the variable. Review the memory you give to workers, which now also handle manual executions. See [Enable queue mode](/deploy/host-n8n/configure-n8n/scaling/enable-queue-mode.md).
* **`N8N_DB_PING_TIMEOUT` removed.** n8n no longer falls back to this variable.
* **What to do:** Set `DB_PING_TIMEOUT_MS` instead. See the [database environment variables](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/database.md).
## Retired capabilities
n8n 3.0 retires some legacy or lower-usage product capabilities. n8n will provide guidance where a migration path or alternative exists.
* **Chat Hub**: n8n 3.0 turns off the [Chat Hub](/build/ways-of-building-workflows/chat-hub.md) module by default. The **Chat** section disappears from the navigation and the Chat Hub endpoints stop responding. Your chat sessions, agents, and messages stay in the database. n8n 4.0 removes the feature.
* **What to do:** If you still need Chat Hub, add `chat-hub` to the `N8N_ENABLED_MODULES` environment variable. The variable holds a comma-separated list, so keep the modules that you already enable, for example `N8N_ENABLED_MODULES=agents,chat-hub`. This keeps Chat Hub available for the n8n 3.x line only, and n8n prints a deprecation warning at startup. Before you upgrade, go to **Settings > Migration Report** and see how this change affects every instance that uses Chat Hub.
* **Workflow import from URL in the editor**: n8n 3.0 removes this. The **Import from URL** option disappears from the editor UI menu.
* **What to do:** Use another [import method](/build/manage-workflows/export-and-import.md): copy-paste, **Import from File** in the editor UI menu, the CLI, or the n8n API. If you automate imports from a URL, fetch the workflow JSON with the **HTTP Request** node and create the workflow through the n8n API.
* **Enable external secrets for project roles setting**: n8n 3.0 removes this. Project editors and admins now get external-secrets access in their projects by default. This applies to n8n Enterprise, where external secrets are available.
* **What to do:** If you used this setting to restrict which project roles reach external secrets, create [custom project roles](/administer/manage-users-and-access/set-permissions-and-roles-rbac/create-custom-roles/create-custom-project-roles.md) with the access you want before you upgrade. Otherwise every project editor and admin gains external-secrets access on upgrade.
* **Ask AI tab in the Code node**: n8n 3.0 removes the **Ask AI** tab from the [Code](/integrations/builtin/core-nodes/n8n-nodes-base.code.md) node. Code you already generated with it stays in the node and keeps running.
* **What to do:** Write JavaScript or Python directly in the **Code** tab.