Skip to main content
Tallwatch sends an embed-style incident message to Discord through a channel webhook. Setup takes about two minutes and needs Manage Webhooks on the server. Point it at a dedicated channel like #incidents rather than your general chat.

​
1. Create the webhook in Discord

1

Open channel settings

Right-click the channel that should receive alerts and click Edit Channel.
2

Add a webhook

In the sidebar, click Integrations → Webhooks → New Webhook. Give it a name like Tallwatch and, optionally, an avatar. Alerts post under this identity.
3

Copy the URL

Click Copy Webhook URL. It looks like https://discord.com/api/webhooks/9876543210/AbCdEf....
The webhook URL is a credential. Anyone who has it can post as this identity in your server. If it leaks, click Delete Webhook in Discord and create a new one.

​
2. Add the channel in Tallwatch

1

Open the channels page

Go to Settings → Alerts → Channels and click Add channel.
2

Pick Discord

Choose the Discord kind and name it for the audience, like Discord #incidents.
3

Paste the URL and test

Paste the URL into Incoming webhook URL, click Save, then Send test alert. The embed should appear in Discord almost immediately.

​
What the alert looks like

One Discord embed per incident event:
  • The monitor name as the embed title
  • An embed color matched to the event, red for opened, green for resolved
  • Inline fields for the event, monitor, URL, failing regions, when it opened, and the last error
  • A link back to the incident in Tallwatch

​
Troubleshooting

The webhook was probably deleted on the Discord side. Discord drops messages to deleted webhooks without an error. Recreate it and update the URL in Tallwatch.It could also belong to a server you’ve lost access to. Re-check the URL under the channel’s integration settings.
The URL is malformed, expired, or revoked. Regenerate it in Discord and paste the new value into Tallwatch.
The webhook still works. Discord attaches the display name at creation time. To change it, edit the webhook in Discord; Tallwatch doesn’t override the name on send.
Tallwatch sends every dispatch immediately, so the delay is on Discord’s side. Discord rate-limits incoming webhooks, roughly 30 requests per minute per webhook, and returns 429 with a retry-after when a burst exceeds it. Check the dispatch history for 429 responses. If a noisy hour keeps hitting the limit, split those monitors across more than one Discord channel.

​
Reference