Skip to main content
DBDock can POST alerts to any HTTP endpoint. This opens the door to Discord, Microsoft Teams, WhatsApp via third-party bridges, and your own internal services.

Configuration

DBDock POSTs a JSON payload to that URL on every backup event.

Payload shape

Success

Failure

Discord

Discord accepts Slack-formatted payloads at its webhook URL with /slack appended:
Set that as your DBDOCK_SLACK_WEBHOOK (not the custom webhook) — DBDock’s Slack alerts format correctly for Discord. For richer Discord messages, use the custom webhook and write your own translator service.

Microsoft Teams

Teams incoming webhook URLs accept Slack-like payloads via the Workflows app. If you’re using the Workflows approach, create a flow “When a Teams webhook request is received” and point DBDOCK_CUSTOM_WEBHOOK at its URL.

WhatsApp

WhatsApp doesn’t have official webhooks. You’ll need a bridge service:
  • Twilio WhatsApp API — POST from your own service that wraps Twilio
  • WhatsApp Business API providers — 360dialog, Gupshup, etc.
Point DBDOCK_CUSTOM_WEBHOOK at your bridge service, which then forwards to WhatsApp.

Writing your own bridge

A minimal Node.js bridge that receives DBDock alerts and forwards them:
Deploy anywhere (Cloud Run, Lambda, your own server) and set DBDOCK_CUSTOM_WEBHOOK to its URL.

Delivery behavior

  • POST with Content-Type: application/json
  • 10-second timeout
  • No retries — if your endpoint is down, the alert is lost (DBDock logs the error)
  • Alert delivery does not block backup completion

Security

  • The webhook URL is a secret if your endpoint doesn’t have its own auth
  • For sensitive deployments, add a shared secret in your endpoint URL or as a query param:
  • Then validate token in your service.

See also

Slack alerts

Built-in Slack support.

Email alerts

SMTP notifications.