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.Documentation Index
Fetch the complete documentation index at: https://docs.dbdock.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Configuration
Payload shape
Success
Failure
Discord
Discord accepts Slack-formatted payloads at its webhook URL with/slack appended:
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 pointDBDOCK_CUSTOM_WEBHOOK at its URL.
- Twilio WhatsApp API — POST from your own service that wraps Twilio
- WhatsApp Business API providers — 360dialog, Gupshup, etc.
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: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
tokenin your service.
See also
Slack alerts
Built-in Slack support.
Email alerts
SMTP notifications.

