Discord
Incident updates in a channel your team already watches
Subscriber updates capability
On this page6
Everything you publish to your status page can also land in a Discord channel: the incident, each update on it, its resolution, and scheduled maintenance with its reminder. The channel is yours, the webhook is yours, and the only thing InBrief holds is the URL you paste in.
Dashboard → Alerts → Channels, then Add channel → Discord. Owners and admins can manage it; it is part of the Subscriber updates capability. Discord carries the incidents you write. Monitor alerts, the "it just went down" message, go to Slack. WhatsApp alerts are coming soon.
Key features
- One destination per status page, with a name, a language and a scope: every service, or only the ones you pick.
- A Send a test button, so you know it lands before your next incident does.
- Pause and resume without losing the webhook; delete when the channel goes.
- The webhook URL is write-only. Once saved it is never shown again, only replaced.
- Automatic pause after repeated failures, said out loud on the screen rather than swallowed.
Connecting a channel
Dashboard → Alerts → Channels. This is the list, with a Discord channel already connected. Add channel opens the form:
Getting the webhook from Discord
- In Discord, open the channel's settings, then Integrations → Webhooks.
- New Webhook, give it a name (this is the name your updates post under) and pick the channel.
- Copy Webhook URL and paste it into the Discord webhook URL field here.
The fields
| Field | What it does |
|---|---|
| Discord webhook URL | The address Discord gave you. It must be a discord.com webhook; anything else is refused as not a Discord destination. The dashboard checks it can be reached when you save. |
| What to call this destination | Shown on this screen and in the audit log. Never sent to Discord. |
| Language | Which of your page's languages the posts are written in. One destination supports one language. Each status page can save only one Discord destination; saving another webhook replaces the existing destination. |
| Every service on this page | Leave it ticked to hear about everything, or untick and choose. An incident that touches none of the chosen services is not posted. |
What is stored
After saving, the card shows the webhook's id as a reference and the date it was stored. The URL itself is gone from view for good: to change it you replace it, which is the only thing the dashboard can do with a credential it will never display. If you delete the webhook in Discord, delete it here too, or replace it.
Confirming it is you
Saving or deleting a destination can ask you to confirm it is you: the dashboard emails you a link, you open it and press the button again. It is the same mechanism you sign in with, used once more for the actions that decide where your incident updates go.
When posts stop arriving
Every delivery is recorded under Last result. If Discord refuses five posts in a row, typically because the webhook was deleted or the channel is gone, the destination is paused and the screen says so. Fix the channel, replace the webhook if you need to, and press Turn updates back on. Nothing is queued while it is paused; the next incident is the first one to arrive.