Like a lot of you I run n8n for clients, and the worst feeling is a workflow quietly breaking and finding out when the client emails. Half the time I couldn’t even tell what changed.
So I built a small free tool: paste two workflow JSON exports → it shows you exactly what changed in plain English (nodes added/removed/renamed/reconfigured), and it ignores noise like dragging a node around. Runs 100% in your browser, nothing uploaded. 
Free n8n Workflow Diff Tool — see what changed between two workflows | Keel
It’s the same diff engine behind a bigger thing I’m building — Keel — a little agent that runs next to your n8n, snapshots every workflow, and alerts you (Slack/Telegram/Discord) the moment one changes or goes offline, with one-click rollback. Your API key never leaves your box; only redacted metadata does.
Would love feedback on the diff tool especially — what would make it genuinely useful for your setup?
1 Like
Welcome @Anthony_Madrid!
The “ignores noise like dragging a node” part is exactly what makes this useful vs a raw JSON diff - most people give up on workflow diffs because of all the positional noise. Feedback for what would make it more useful: showing the actual parameter-level change inside a reconfigured node (e.g. “HTTP Request - URL changed from X to Y”) rather than just “node reconfigured” would cut debugging time a lot when you’re trying to pinpoint a regression. Keel’s snapshot + Telegram alert combo is the right architecture for production n8n setups.
Appreciate the welcome! You nailed the intent. Raw JSON diffs are noise; cutting the positional churn so you only see real changes is the whole point.
And parameter-level diffs are next, “HTTP Request: URL changed X → Y,” not just “node reconfigured.” That’s the line between a diff you glance at and one you trust in production.
Means a lot coming from someone who’s clearly run n8n in anger. Would love your eyes on it as it develops.