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

Description and use

Self-hosted n8n users must migrate to Docker and address breaking changes in v3.0, such as the 60‑second Code node timeout, removal of Function/Cron/Interval nodes, AI Agent v1 retirement, and Slack signing secret requirement.

Problem

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

Outcome

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

Workflow

• 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

Evidence

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

Source

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

Source

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

Source

The Slack API credential now requires a signing secret.

Source