Discord โ
Send rich embed notifications to Discord channels via webhooks. Discord is the easiest notification channel to set up โ just create a webhook and paste the URL.
Overview โ
- ๐จ Rich Embeds โ Color-coded status indicators with structured fields
- โก Instant Delivery โ Real-time notifications via Discord's webhook API
- ๐ง Customizable โ Set bot username and avatar per notification channel
- ๐ฑ Cross-Platform โ Desktop, mobile, and web notifications via Discord
Configuration โ
| Field | Description | Default | Required |
|---|---|---|---|
| Webhook URL | Discord webhook URL | โ | โ |
| Username | Bot display name in Discord | Backup Manager | โ |
| Avatar URL | Bot avatar image URL | Discord default | โ |
Setup Guide โ
1. Create a Discord Webhook โ
- Open your Discord server
- Go to Server Settings โ Integrations
- Click Webhooks โ New Webhook
- Choose the target channel
- (Optional) Set a custom name and avatar
- Click Copy Webhook URL
Dedicated Channel
Create a dedicated #backups or #alerts channel to keep notifications organized and avoid noise in general channels.
2. Configure in DBackup โ
- Go to Notifications in the sidebar
- Click Add Notification
- Select Discord Webhook
- Paste the webhook URL
- (Optional) Set a custom username and avatar URL
- Click Test to verify
- Save
3. Test the Connection โ
Click Test to send a test notification. You should see a message appear in your Discord channel within seconds.
Message Format โ
Discord notifications use rich embeds with colored sidebars:
| Color | Meaning | Events |
|---|---|---|
| ๐ข Green | Success | Backup complete, restore finished, user created |
| ๐ด Red | Failure | Backup failed, restore failed, system error |
| ๐ต Blue | Informational | User login |
| ๐ฃ Purple | System | Config backup |
Each embed includes:
- Title โ Event type (e.g., "Backup Successful")
- Description โ Summary message
- Fields โ Structured key-value data (job name, duration, size, etc.)
- Timestamp โ When the event occurred
Multiple Webhooks โ
You can create multiple Discord notification channels pointing to different webhooks. For example:
#production-backupsโ Critical production job alerts#dev-backupsโ Development environment notifications#system-alertsโ Login, restore, and error events
Troubleshooting โ
Invalid Webhook Token โ
Discord returned 401: Invalid Webhook TokenSolutions:
- Verify the webhook URL is complete and correct
- Check the webhook hasn't been deleted in Discord
- Regenerate the webhook in Server Settings โ Integrations
Rate Limited โ
Discord returned 429: You are being rate limitedCause: Too many messages sent in a short period. Discord limits webhook requests.
Solution: Reduce notification frequency. Avoid setting every job to "Always" notify if you run many jobs per minute.
Webhook Not Found โ
Discord returned 404: Unknown WebhookSolutions:
- The webhook may have been deleted
- The channel may have been deleted
- Create a new webhook and update the configuration
Best Practices โ
- Use dedicated channels โ Don't spam general channels
- Set meaningful usernames โ Use names like "DBackup Production" to identify the source
- Notify on failure for most jobs โ Reduces noise
- Use "Always" for critical production โ Never miss a backup result
- Protect webhook URLs โ Treat them like passwords