If you run n8n for clients, you know the nightmare: a workflow quietly breaks and you find out from the client.
Keel watches every n8n workflow and tells you what changed. Diffs, alerts, 1-click rollback. Your secrets stay on your box.
Freeπ
https://t.co/KHOuMVuTQ0
shipped 3 free n8n tools this week. funniest part is the analyzer roasting my own workflows for hardcoded secrets. self-own as a service π οΈhttps://t.co/KHOuMVuTQ0
Second: paste a workflow β watch the hardcoded secrets get stripped. Because your n8n JSON is leakier than you think. π https://t.co/ZRmdGhTxs8 #lfg
So I built free tools to fix the blind spots. First: paste two workflow versions β see exactly what changed, plain English, in-browser, no signup. π https://t.co/PdCf9wghrF #n8n#ai
Running n8n for clients has one recurring nightmare: a workflow quietly breaks, and you find out when the client emails you. You don't even know what changed. #n8n#AI
The first time I pointed my own monitoring agent at my real n8n, it caught a webhook secret leaking in a workflow export.
Fixed the redaction, shipped it. Dogfooding > unit tests. Building Keel in public π οΈ
Your n8n workflows probably have secrets hardcoded in HTTP headers.
Here's a free tool that strips them right in your browser β so you can safely back up or share a workflow. Watch the redaction happen live:
https://t.co/kyUcWEZzEJ
n8n has no undo. Edit a workflow, save, and the previous version is just⦠gone.
So I made a free tool: paste two versions, see exactly what changed in plain English. In-browser, no signup.
https://t.co/M8sFjqX0K2