Discord alerts
Post alerts to a Discord channel through a webhook URL: setup, the color of each alert and how failures are logged.
Last reviewed
On this page
The Discord channel posts each alert as a colored message to a channel through a Discord webhook URL. No bot or app install is needed. This page covers the setup, what a message looks like and how failures show up. The rules that decide when an alert is sent are on the alert rules page.
Set up a Discord notification
Create a webhook in Discord
In Discord, open the channel's settings and choose Integrations, then Webhooks, and create a webhook. Copy its URL. You need the Manage Webhooks permission on the channel.
Add the notification in OctoPing
On the site's Notifications page, choose Add Notification and set Notification Type to Discord. Paste the URL into Discord Webhook URL. The form accepts a URL that starts with
https://orhttp://.Choose the triggers and send a test
Choose Send Test. A message appears in the channel, and the result appears on the page.
What a message looks like
OctoPing posts one embed per alert. The title is the alert's subject line, the same text an email would carry. The description is the alert's message, cut at 2048 characters. The footer reads OctoPing and the embed carries a timestamp. For a website, the title links to the site in OctoPing. A heartbeat embed has no link.
The color of the embed shows the kind of alert.
| Color | Alerts |
|---|---|
| Red | Site down, Heartbeat missed |
| Green | Recovered |
| Yellow | Content changed, HTTP status changed |
| Blue-violet | DNS records changed, WHOIS details changed, Hosting changed, Test send |
| Pink | robots.txt changed |
| Orange | SSL certificate expiring, Domain expiring, Checker blocked notice |
| Gray | Slow response, and any alert without a color of its own |
Discord has no layout of its own for each alert type. The description is the same plain text an email or a webhook carries, so a Discord alert carries the same text as the email and the webhook message.
Delivery and failures
OctoPing makes one attempt per alert, with a 10-second limit. A failed attempt isn't retried, and the log records it as Failed with the reason. Discord answers an invalid or deleted webhook with an error status, and the Error column shows that status. The next alert is the next attempt.
| Error text | What it means |
|---|---|
| No Discord webhook URL configured | The notification has no URL. Edit it and paste one. |
| An HTTP error naming a status code | Discord rejected the request. A 404 means the webhook was deleted, and a 429 means Discord is slowing the sender down. Create the webhook again if it was deleted. |
Related
- DocsAlert rulesHow a failed check becomes an alert: the retry threshold, the repeat interval, the four triggers, recovery, the default notification, the log and what a maintenance window holds back.
- DocsSlack alertsConnect Slack to a workspace, post alerts to a channel, and what the log shows when a message fails.
- DocsWebhooksThe JSON payload for every website and heartbeat event, the request headers, how to verify the HMAC signature in Python, Node.js, PHP and Go, and how retries work.
- FeatureWebsite alerts by email, Slack, Discord, webhook and pushChoose where alerts go, how many failures it takes to send one and how often reminders repeat. Recovery messages and a log of every attempt are included.
- GuideSend uptime alerts to a Discord channelGet down and recovery alerts for your sites in a Discord channel your team already watches.