Know the moment an n8n workflow changes or breaks.
The worst way to learn a client's automation broke is an angry email. Keel watches every workflow and tells you first — what changed, when, and whether it's still running.
Silent breakage is the default
n8n won't tell you when a workflow is edited, deactivated, starts failing, or the instance goes quiet. You find out when something downstream breaks — usually when the client notices before you do.
How Keel alerts you
Change alerts
Edited, deactivated, unexpectedly published, credentials changed — routed to Slack, Telegram, or Discord with a plain-English diff.
Failure & offline detection
Keel flags failing executions and marks a connection offline if the agent stops heartbeating, so a dead instance doesn't go unnoticed.
Per-client routing
Send each client's alerts to the right channel, so the noise stays organized as you scale.
No payloads, ever
Alerts carry metadata and summaries — never your execution data. Secrets are redacted on the agent before anything leaves.
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
Can n8n send me an alert when a workflow changes?
Not on its own. n8n can notify inside a workflow run, but it won't tell you when the workflow itself is edited, deactivated, or goes offline. Keel watches from outside and does.
Which channels are supported?
Slack, Telegram, and Discord, with per-client routing.
Does the alert include my data?
No. Alerts contain change summaries and metadata only — execution payloads and secrets never leave your server.
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.