Your n8n workflow broke — find out what changed.
A workflow that worked yesterday is failing today, and n8n won't tell you what changed. The fastest path to a fix is knowing exactly what's different. Here's how to get there.
"It worked yesterday" with no way to prove it
Without version history you're debugging blind: was it an edit, a credential change, an n8n upgrade, or an upstream API? n8n overwrites the previous version on save, so you can't simply compare to last week.
How to find what broke
Diff against a known-good version
If you have an earlier export, compare it to the current workflow to see exactly what changed. Free, in-browser: keel.tools/tools/n8n-diff.
Catch it next time, automatically
Keel snapshots and diffs every change, so the next break comes with a plain-English answer to "what changed?" already attached.
Get alerted first
Failure and offline detection means you hear about a break from Keel, not from your client.
Roll back fast
Restore the last known-good version as importable JSON in one step.
Find out what changed before your client does.
Keel runs a lightweight agent next to your n8n — snapshots, diffs, alerts, and rollback, with your secrets and API key never leaving your box. Free forever on one instance.
Questions
Why did my n8n workflow suddenly stop working?
Common causes: someone edited it, a credential expired or changed, an n8n version upgrade changed node behaviour, or an upstream API changed. Diffing against a known-good version isolates an edit fast.
How do I see what changed in my workflow?
Paste a prior export and the current one into a diff tool. There's a free one here: keel.tools/tools/n8n-diff. Keel does this automatically on every change.
How do I stop this from happening again?
Continuous monitoring: snapshot every change, diff it, and alert on changes/failures so you catch issues before they cause downtime.
See every change before it breaks a client.
Point Keel at your n8n estate this week. Free 14-day trial, no card, your keys never leave your infrastructure.