Discord
Create the webhook
Section titled “Create the webhook”- In Discord, open the channel’s settings → Integrations → Webhooks → New Webhook.
- Copy its URL.
That URL is a secret: anyone who has it can post to the channel as the webhook.
Add the destination
Section titled “Add the destination”- Go to Add destination → Discord.
- Name it and paste the channel webhook URL.
- Save, then click Send test to confirm a message shows up in the channel.
What alerts look like
Section titled “What alerts look like”Each alert is one Discord message: a severity marker, the title, the source and resource it’s about, the detail body, and links back to the incident and the sender’s own view. Discord edits that same message in place as the incident changes — acknowledged, snoozed, resolved — rather than posting a new one each time.
Options
Section titled “Options”- Send recovery and state updates — off, and this channel is only told when something breaks.
- Enabled — off holds the destination without deleting it.
- Quiet-hours threshold — the severity floor this destination still hears during quiet hours.
When Discord pushes back
Section titled “When Discord pushes back”Discord counts a rejected request against the address it came from, and restricts that address if they keep coming. If a burst of Discord webhooks answers 401, 403 or 429 at once — several deleted webhooks, say — InfraInbox stops sending to Discord for about five minutes rather than keep asking. The notices are queued, not lost: they go out when the pause ends, and they appear as pending in Deliveries meanwhile. Destinations of other kinds are unaffected.
A single deleted webhook does not cause this; it simply marks that one destination broken.
Rotating the webhook
Section titled “Rotating the webhook”Generate a new webhook URL from the channel’s Integrations settings and paste it into this destination’s edit form.
- Routing rules — send specific incidents here
- Slack — the same idea, without in-place edits