Notification Channels
DBackup supports multiple notification channels to keep you informed about backup status, system events, and user activity. Choose based on your team's communication platform and requirements.
Supported Channels
| Channel | Type | Best For |
|---|---|---|
| Discord | Webhook | Team chat, gaming communities, dev teams |
| Slack | Webhook | Workplace communication, DevOps teams |
| Microsoft Teams | Webhook | Enterprise environments, Microsoft 365 |
| Gotify | REST API | Self-hosted setups, home labs |
| ntfy | HTTP/Topic | Self-hosted or public push notifications |
| Generic Webhook | HTTP | Custom integrations (PagerDuty, etc.) |
| Telegram | Bot API | Instant push to chats, groups, channels |
| SMS (Twilio) | SMS | Critical alerts to any mobile phone |
| Email (SMTP) | SMTP | Formal alerts, per-user notifications, audit trail |
Choosing a Channel
Discord
Pros:
- Quick setup (just a webhook URL)
- Rich embeds with colors and structured fields
- Great for small teams and dev communities
Cons:
- Not suitable for formal/enterprise notifications
- Webhook URLs can be leaked if not handled carefully
Best for: Development teams, home lab admins, small organizations.
Slack
Pros:
- Industry-standard workplace messaging
- Block Kit for rich, interactive formatting
- Channel override for routing notifications
Cons:
- Requires Slack workspace access
- Webhook URLs tied to specific channels
Best for: DevOps teams, engineering organizations, startups.
Microsoft Teams
Pros:
- Native Microsoft 365 integration
- Adaptive Cards for structured content
- Enterprise-grade compliance
Cons:
- Webhook setup requires Power Automate / Workflows
- More complex setup than Discord or Slack
Best for: Enterprise environments, Microsoft 365 organizations.
Gotify
Pros:
- Self-hosted — full control over notification infrastructure
- Priority levels with automatic escalation on failures
- Markdown formatting
- Android app with real-time push
Cons:
- Requires running a Gotify server
- No native iOS app (web client only)
Best for: Self-hosted enthusiasts, home lab admins, privacy-conscious users.
ntfy
Pros:
- Works without any server setup (public ntfy.sh)
- Topic-based — subscribe from any device instantly
- Android, iOS, and web clients
- Can also be self-hosted
Cons:
- Public topics are not private (use random topic names or self-host)
- Simpler formatting than rich embed platforms
Best for: Quick setup, mobile push notifications, self-hosted or public usage.
Generic Webhook
Pros:
- Works with any HTTP endpoint
- Customizable payload templates
- Supports authentication headers
Cons:
- Requires endpoint setup on the receiving end
- No rich formatting (plain JSON)
Best for: Self-hosted notification services (Gotify, ntfy), monitoring tools (PagerDuty, Uptime Kuma), custom integrations.
Telegram
Pros:
- Instant push notifications to any device
- Free — no server or subscription required
- Groups and channels for team alerts
- Silent mode for non-urgent notifications
Cons:
- Requires creating a bot via @BotFather
- Getting a Chat ID can be unintuitive
Best for: Personal alerts, small teams, mobile-first users, home lab admins.
SMS (Twilio)
Pros:
- Works on any mobile phone (no app needed)
- Highest visibility — SMS are hard to ignore
- Reliable enterprise-grade delivery
Cons:
- Costs money per SMS segment
- Requires a Twilio account
- Limited message length
Best for: Critical failure alerts, on-call escalation, environments where internet-based messaging is unreliable.
Email (SMTP)
Pros:
- Universal — everyone has email
- HTML formatting with status colors
- Per-user delivery for login/account events
- Audit trail
Cons:
- Requires SMTP server access
- May land in spam if not configured properly
Best for: Formal alerts, compliance requirements, per-user notifications.
Adding a Notification Channel
- Navigate to Notifications in the sidebar
- Click Add Notification
- Select the channel type from the adapter picker
- Fill in the configuration details
- Click Test to send a test notification
- Save the configuration
Two Notification Layers
DBackup has two independent notification systems that share the same channels:
| Layer | Configured In | Purpose |
|---|---|---|
| Per-Job Notifications | Job → Notifications tab | Alerts for individual backup jobs |
| System Notifications | Settings → Notifications | System-wide events (login, restore, errors) |
See Notifications Feature Guide for detailed configuration of per-job and system notifications.
Next Steps
Choose your notification channel for detailed setup instructions:
- Discord — Webhook-based rich embeds
- Slack — Block Kit formatted messages
- Microsoft Teams — Adaptive Card notifications
- Gotify — Self-hosted push notifications
- ntfy — Topic-based push notifications
- Generic Webhook — Custom JSON payloads
- Telegram — Bot API push notifications
- SMS (Twilio) — SMS text message alerts
- Email (SMTP) — HTML email via SMTP