n8n 3.0 Is Docker-Only: What Self-Hosters Need to Change Before Upgrading

说明与用途

自托管 n8n 用户需要迁移到 Docker 并处理 3.0 版的破坏性更改，包括 Code 节点 60 秒超时、Function/Cron/Interval 节点移除、AI Agent v1 退休以及 Slack 签名密钥要求。

Self-hosted n8n users must upgrade to Docker-only installation and address multiple breaking changes before version 3.0 release.

After following the checklist, self-hosted n8n users can upgrade to 3.0 without workflow failures and maintain continuous operation.

Export workflows and credentials
Stand up Docker container for n8n
Import and test workflows in Docker
Search for Function, Cron, Interval nodes and replace with Code or Schedule Trigger
Identify Code nodes exceeding 60s and refactor or offload heavy work
Move AI Agent v1 workflows to Tools Agent and test with real prompts
Add Slack signing secret to credential and verify Slack workflow
Run Docker instance alongside old instance for a full day of real traffic
Backup workflows and credentials before final upgrade

Self-hosted n8n becomes Docker-only in 3.0. npm and npx installs stop being supported.

The Code node timeout goes from 5 minutes down to 1 minute.

The Function, Cron, and Interval nodes are removed in 3.0.

The Slack API credential now requires a signing secret.