Upgrade Watch: three n8n workflows that find what breaks before n8n 3.0 arrives
Disclosure first
This page contains an affiliate link. If you buy through it, we earn a commission at no extra cost to you. The vendor provided a free copy of this pack. We read the workflow files and the documentation; we did not run an upgrade ourselves, and the test results below are the vendor's, reported in their LIMITS.md.
The short answer
n8n 3.0 lands in early December and removes 37 nodes. A published workflow that still uses one does not start, so its trigger stops firing and nothing tells you. Upgrade Watch is three workflows that run inside your own n8n: a scan before the upgrade that lists every workflow you have to fix, a baseline that records how each workflow normally runs, and a check that watches for 48 hours after n8n restarts and names any workflow that did not come back. The pack ships with a fix guide for each item and a runbook for the day itself.
What the three workflows do
- Pre-upgrade scan reads every workflow through the n8n API and emails one list, in order of severity: published workflows that stop after the upgrade because they contain a removed node; workflows whose node fails when it runs on 3.0 (an AI Agent in a removed mode, the old Edit Image, Execute Workflow loading from a file or URL); workflows that call a sub-workflow with a removed node; and workflows whose behaviour changes, such as Compare Datasets or Filter with Always Output Data. When there is nothing to report it sends nothing and shows "Upgrade scan: nothing to fix".
- Baseline runs daily and records, per workflow, the usual gap between runs, sampled from the last 20 executions. That is what makes "late" a meaningful word after the upgrade, instead of a fixed number that fits nobody.
- After upgrade check starts when n8n starts, then runs every 15 minutes for 48 hours. It compares the new runs against the baseline, and names each workflow that has not come back, once.
Two documents matter as much as the workflows. FIX-GUIDE.md gives the replacement for each line the scan prints, node by node. RUNBOOK.md is the upgrade day itself: stop n8n, copy the data folder, start the new image on the same folder, then read the check emails.
What the vendor says they tested
Their LIMITS.md is specific enough to be useful, which is rare in this category. Two clean instances, n8n 2.43.6 upgraded to the 3.0.1 pre-release in Docker, the data folder copied as a backup first, the same encryption key, mail to a local test server.
The clean upgrade: the scan said nothing to fix, the baseline recorded a one-minute gap for a one-minute workflow, and after the upgrade the workflow ran and no message was sent. With the all-clear message switched on, one message arrived saying every scheduled workflow ran.
The upgrade with problems: 16 test workflows plus the 9 Silent Failure Watch workflows and these 3, 28 published in total. The scan listed exactly the expected workflows in each section, including a published sub-workflow with a removed node and a workflow whose draft had a Cron but whose published version did not. The vendor reports 17 checks passed for the agency version on 31 October 2026.
What they did not test is written down too: the check ran every minute instead of every 15 during the test, 3.0.1 is a pre-release, and the client version was tested with two real client instances, not more.
The limits worth knowing
- It needs a self-hosted n8n with an API key. Same requirement as n8n Cloud's paid plans and not the free trial, so the trial cannot run this.
- It is a list, not a migration. The scan tells you which workflows to fix and the fix guide tells you what to replace, but you still edit them by hand. n8n's own Migration Report can do some replacements for you.
- 48 hours is the default watch window. That covers any workflow running at least every 31 hours. Weekly workflows need
watch_hoursset to 260, which the README says plainly. - A clean result is not a guarantee. The scan knows removed nodes and known behaviour changes. If you changed something else on the same weekend, it will not explain that.
- The agency version is the Client work tier at $129: one scan across up to 30 client instances, 16 connectors tested. The $39 tier is your own n8n only.
Who it is for
You self-host n8n, you have more than five or six workflows doing real work, and you are going to upgrade in December. The scan alone is worth the price if it saves you one silent week. If you have two workflows and you check them daily, the free guide on this site is enough: n8n 3.0 removes the Function node.
If you want it
Affiliate link. We earn 70 percent of a sale made through it. Code VOXAU20 takes 20 percent off. $39 for your own n8n, $129 for the version that scans client instances.
Questions people are asking
Do I need this if I already have their Silent Failure Watch?
They cover different things. Silent Failure Watch watches whether workflows run. Upgrade Watch is about the 3.0 upgrade specifically: what will not start, and what did not come back afterwards. They share the same two credentials, so if one is installed the other is quicker to set up.
Does it work on n8n Cloud?
The free trial cannot, because Cloud blocks API access there. Paid Cloud plans expose the API, but the vendor tested self-hosted Docker only, so treat Cloud as unverified.
What if I have already upgraded?
The pre-upgrade scan is the main value and it is meant to run before. After the fact, the after-upgrade check still helps if you have a baseline, and n8n's own Migration Report lists what changed.
How long does setup take?
Import three workflows, set two credentials and a few Settings values, publish two of them, run the scan by hand once. Reading the fix guide takes longer than the setup.
Is the $129 version worth it?
Only if you run n8n for clients. It scans up to 30 client instances and reports per client. For one instance, the $39 tier is the whole product.
Sources
Krafera Upgrade Watch: README, LIMITS.md, FIX-GUIDE.md and RUNBOOK.md from the pack, October 2026 · n8n docs, v3.0 breaking changes · n8n blog, "Introducing n8n 3.0", 27 October 2026.