Connect Discord

Post InfraNest alerts into a Discord channel — handy for communities and teams that live in Discord.

#Connect it in InfraNest

Go to Integrations → Discord and select Connect (or Add account if you already have a Discord destination). From Alerts → Destinations, Add destination takes you to the same place. There are two ways in.

One-click connect (recommended, when offered): select Connect, then on Discord's screen pick the server and the channel and select Authorize. Discord creates the webhook for InfraNest, so there is nothing to copy. You need the Manage Webhooks permission on that server.

Post into a Discord channel with a webhook you create yourself:

1. In Discord, open the channel's settings, then go to Integrations → Webhooks.
2. Select New Webhook, give it a name (like "InfraNest"), and pick the channel.
3. Select Copy Webhook URL.
4. In InfraNest, give the destination a Name — the team or channel it reaches — and paste the Incoming webhook URL. Select Connect.

Either way, InfraNest then offers to Send a test. Do it, and check the message appears in the channel.

#What arrives in Discord

Each alert is a message in the channel: what happened in bold, then the details. Alerts never ping anyone in the channel. When the problem is over, InfraNest edits the original message to start with ✅ Resolved after … min (for alerts up to 7 days old), and posts a short message naming the alert it closes.

#The destination's page

Under Integrations → Discord → Connections & settings, select the destination to open its page.

• Connection details: the webhook URL it sends to. Paste a new one to replace it, then select Save.
• What should this destination hear?: All events or Urgent only.
• Hours (optional): set From and Until, and optionally the days. Outside those hours the destination hears critical events only, so an outage still gets through.
• The ⋯ menu at the top has Test connection, Rename account, Disable integration (and Enable integration to switch it back on) and Disconnect.

In the destination list, the ⋯ menu next to each destination has Send test, Edit (its page) and Delete. A deleted destination can be restored from Recently deleted for 14 days.

#Check it keeps working

Under Alerts → Destinations, each destination shows its last test: Last test delivered, Last test sent … not confirmed yet or Last test failed. Switch on Monthly test to have a test alert sent there once a month, so a broken path shows up before an outage does. Each test message has an I got it link: click it to confirm someone saw it.

If Discord starts turning alerts away, the destination says Not delivering and Alerts are not reaching this destination, and whoever manages it is told by email and in the bell. It is never switched off: InfraNest keeps sending, emails each alert it turned away to whoever manages it instead, and keeps them for 7 days so you can Send them here now once it works again. See A destination says it is not delivering.

#Send alerts to Discord

Once the destination is saved, choose it when you decide which alerts go where. See Alerts and destinations.

#Good to know

• The webhook URL is stored securely and never shown again after saving. Anyone holding it can post in that channel, so treat it as a secret.
• One destination posts to one channel. Add another destination for a different channel.
• If someone deletes the webhook in Discord, alerts stop arriving and the destination says Not delivering. Create a new webhook and paste it under Connection details.

#Related articles

• Alerts and destinations
• A destination says it is not delivering