Skip to content
downpipes docs

Send downpipes alerts to Slack

Slack receives downpipes alerts through an incoming webhook, as a notification. Slack is not an incident tool, so nothing here de-duplicates or auto-resolves. When you need that, send to one of the incident platforms (PagerDuty, Opsgenie or Jira Service Management, or ServiceNow) as well as or instead of Slack.

What you need

  • A Slack workspace where you can create an incoming webhook for the channel you want alerts in.
  • Access to the downpipes console with the notify-config capability (Operator, Approver or Owner) to add and test the channel.

Set it up

  1. In Slack, create an Incoming Webhook for the target channel and copy the webhook URL.
  2. In the downpipes console, open Notifications, choose Add a channel and pick Slack (incoming webhook). Adding a channel needs the notify-config capability, so an Operator, Approver or Owner can add one.
  3. Paste the webhook URL into the HTTPS URL field. It must be https and carry no embedded credentials. Name the channel and save it, then a rule routes events to it.
  4. Choose Test on the channel to confirm delivery without sending real alert content, then check the message arrived in Slack.

Good to know

  • Notification only, by design. Each alert posts as a message with a severity glyph and a one-line summary. Slack does not track incident state, so a recovery arrives as another message rather than resolving an earlier one. Route to an incident platform when you need dedup and auto-resolve.
  • The message carries no backup contents. downpipes builds the text from the event, the severity, the downpipe name and a short detail, never a secret, a key or the data being backed up.

Last updated .