Skip to content
downpipes docs

Send downpipes alerts to your own webhook

A webhook channel posts each event to any HTTPS endpoint you run, in a documented JSON shape you map yourself. This is the channel to point at your own automation or at a tool without a dedicated channel here.

What you need

  • An HTTPS endpoint you control that can accept a JSON POST.
  • Access to the downpipes console with the notify-config capability (Operator, Approver or Owner) to add and test the channel.

Set it up

  1. Stand up, or choose, the HTTPS endpoint that will receive the events. It must be https and must not be a workers.dev host.
  2. In the downpipes console, open Notifications, choose Add a channel and pick Webhook (generic HTTPS POST). Adding a channel needs the notify-config capability, so an Operator, Approver or Owner can add one.
  3. Paste the endpoint 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 row to confirm delivery without sending real alert content, then check your endpoint received the POST.

What lands at your endpoint

Each event arrives as a downpipe-event-v1 JSON body:

{"kind":"downpipe-event-v1","at":"2026-07-05T04:14:08.123Z","event":"backup-failure","severity":"critical","downpipe":{"id":"dp_9f2","name":"prod-kv"},"detail":"prod-kv backup failed"}

The downpipe object is omitted for an account-level event. Map these fields to whatever your endpoint or downstream tool expects.

Good to know

  • The outbound call is screened like every channel. downpipes re-screens the destination host at send time with the same egress guard the other channels use, and refuses an internal or link-local target unless you have explicitly opted that channel in. The body carries only operational facts (the event, severity, downpipe id and name, a one-line detail and the time), never a secret or the data being backed up.
  • No dedup or auto-resolve unless you build it. downpipes posts the same event shape every time and sends no dedicated resolve on this channel, so any correlation or resolve is something your endpoint derives from the fields, for example by keying on the downpipe id and reading the event and severity.

Last updated .