Get n8n alerts in Slack.
You can build a Slack node into a single workflow, but that won't tell you when the workflow itself is edited, deactivated, starts failing, or the instance goes quiet. Keel watches all of that and posts a plain-English summary to Slack.
A Slack node only covers one happy path
Wiring a Slack message into a workflow notifies you when that workflow runs as designed. It says nothing when someone changes the workflow, it gets turned off, credentials break, or n8n itself stops responding — exactly the events you most need to hear about.
What Keel posts to Slack
Change alerts
A workflow was edited, renamed, deactivated, or unexpectedly published — with a plain-English diff of what changed.
Failure & offline
Execution failures and a silent/offline instance, so a dead automation doesn't sit unnoticed.
Per-client channels
Route each client's alerts to the right Slack channel so the noise stays organized as you scale.
Summaries, not payloads
Alerts carry a readable summary and metadata — never your execution data, which never leaves your box.
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
How do I send n8n alerts to Slack?
Add a Slack channel in Keel and it posts workflow changes, failures, and offline events automatically — no per-workflow wiring. Telegram and Discord work the same way.
Can I get alerts for self-hosted n8n?
Yes — Keel's agent runs next to your self-hosted instance and only makes outbound calls, so Slack alerts work behind a firewall.
Do alerts contain my data?
No — only change summaries and metadata. Execution payloads and secrets stay on 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.