Your n8n 3.0 upgrade needs a migration check first

n8n 3.0 shipped in beta today, and for anyone running a self-hosted instance through npm or npx, it changes how you install the tool before it touches a single workflow.

What n8n 3.0 actually changes

n8n's own blog frames 3.0 as a release built around reliability, stability, and security, not new automation features. The 2.x line has been shipping fast all month: 2.43 landed October 6, 2.43.5 and 2.44 followed within the week, and 2.45 shipped October 20. Version 3.0 is the cleanup that follows that sprint. It drops the npm and npx install path for self-hosted instances entirely, removes a long list of nodes that have had replacements for a while, and tightens several defaults that were left loose for backward compatibility.

The n8n 3.0 upgrade checklist

1. 1

   Run the migration report

   Open Settings, then Migration Report in your current instance. It lists every workflow and setting that 3.0 will affect, before you touch anything.

2. 2

   Move off npm if you're still there

   If you installed with npm or npx, 3.0 doesn't publish a runnable npm package at all. Switch to the official Docker setup script or a Docker Compose file with Postgres first.

3. 3

   Back up the database

   Standard practice before any major version jump, and worth doing here given how many defaults move at once.

4. 4

   Add a Slack signing secret

   3.0 requires one on the Slack API credential. Without it, any workflow using a Slack Trigger stops receiving events, with no error to flag it.

5. 5

   Check Gmail Trigger workflows

   Drafts stop counting as new mail unless you turn on Include Drafts, and sent or scheduled emails no longer fire the trigger at all.

6. 6

   Swap out removed nodes

   Function, Cron, Interval, Workflow Trigger, Read/Write Binary File, and a handful of legacy AI nodes are gone in 3.0. The migration report flags each one with its replacement.

Defaults that will quietly break things

• Task runner timeout drops from 300 seconds to 60, so long-running Code nodes may start timing out.
• Decompression limits drop to 256 MiB and 1,000 entries, which can affect workflows that unzip large vendor exports.
• The SSRF block list gains four more ranges, including 100.64.0.0/10, which can quietly block internal HTTP calls that used to work fine.
• The binary data folder renames from ~/.n8n/binaryData to ~/.n8n/storage. n8n refuses to start if both folders exist on disk.
• Chat Hub ships off by default. Re-enable it with the N8N_ENABLED_MODULES environment variable if you rely on it.

If your business runs lead routing, invoice follow-ups, or client onboarding through n8n, this is the week to open that migration report and see what it flags, before beta becomes the default install. Send me what you're running and we can walk through what 3.0 actually touches.