title: "Discord notifications" description: "Route BoxWatch alerts to a Discord channel via webhook URL." last_updated: "2026-05-24"

Discord notifications

Post BoxWatch alerts to a Discord channel via a channel webhook. One Discord URL per account. Messages use Discord embeds with color-coded severity.

In your Discord server, right-click the target channel and pick Edit Channel.
Go to Integrations → Webhooks → New Webhook.
Name it (e.g. "BoxWatch alerts"), optionally upload an avatar, and click Copy Webhook URL.
The URL looks like https://discord.com/api/webhooks/123.../abc....

Anyone with the URL can post to that channel — treat it like a secret.

BoxWatch validates that the URL starts with https://discord.com/api/webhooks/ before saving. Anything else is rejected.

Each alert posts as a Discord message with the alert type, the entity name, and a link to the dashboard. Examples:

🚨 Process down: postgres on db-prod-1
https://boxwatch.app/dashboard/servers/14

⚠️ Cert expiring: api.example.com
Target: https://api.example.com
https://boxwatch.app/dashboard/uptime/119

Discord renders the link as a clickable preview tile when its embed unfurler can reach BoxWatch.

Dashboard → Account → Notifications → Test Discord. BoxWatch posts a synthetic alert. Or from the API:

POST/auth/test-webhook

Auth: bearer

Body: { "platform": "discord" }.

404 from Discord — the webhook or its channel was deleted. Create a new webhook in Discord and update BoxWatch.
401 / 403 — the webhook URL token is invalid. Re-copy the URL from Discord — make sure you grabbed the whole thing including the trailing token.
Rate-limited (429) — Discord limits each webhook to 30 messages per minute. Heavy alert volume from one account can hit this; consider switching to a generic webhook with a custom Discord bot for higher throughput.
Test works but real alerts don't show — check Dashboard → Alerts → History to confirm the alert actually dispatched. If it did, you may be looking at the wrong channel — re-check the webhook's target.