How to Fix n8n Workflows That Stopped Working After an Update
n8n workflows broke after updating? Fix the six real causes: failed migrations, lost keys, renamed variables, removed nodes, and broken webhooks.
n8n workflows broke after updating? Fix the six real causes: failed migrations, lost keys, renamed variables, removed nodes, and broken webhooks.
n8n 3.0 cut the Code node timeout from 5 minutes to 60 seconds. Learn to diagnose the timeout, restore the old limit, or restructure long workflows.
Use n8n workflows as MCP tools in Claude Code: enable the MCP server, connect via OAuth or API key, expose workflows, then run them from the terminal.
Migrate n8n from npm to Docker before n8n 3.0 drops npm support. Back up ~/.n8n, protect the encryption key, and boot a pinned 2.x image first.
Upgrading to n8n 3.0? This checklist covers every breaking change: Docker-only deployment, 35+ removed nodes, security defaults, and a staged upgrade path.
Fix n8n CVE-2026-44791 (CVSS 9.4): upgrade self-hosted n8n to 1.123.43, 2.20.7, or 2.22.1, or disable the XML node via NODES_EXCLUDE. Docker and npm steps.
Run n8n in queue mode: a main instance plus Redis-backed worker processes for parallel executions. Docker Compose setup guide, verified on n8n 2.41.4.
Update self-hosted n8n safely: Docker Compose, Docker, and npm upgrade paths with backups, database migrations, rollback steps, and five real fixes.
Set up n8n with Docker Compose, Postgres, and queue mode with Redis workers. Complete compose file, .env template, safe upgrades, backups, and five real fixes.
Install n8n on an Ubuntu VPS with Docker Compose, Postgres 18, and free HTTPS via Caddy. Verified against n8n 2.40.7, including the new npm deprecation warning and four real-world fixes.