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 likeDocumentation Index
Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt
Use this file to discover all available pages before exploring further.
#incidents rather than your general chat.
1. Create the webhook in Discord
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.2. Add the channel in Tallwatch
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
- A short description plus inline fields for failing regions, duration, and the consensus rule
- A link back to the incident in Tallwatch
Troubleshooting
The test sent, but nothing arrived
The test sent, but nothing arrived
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.
`webhook_invalid` in the dispatch history
`webhook_invalid` in the dispatch history
The URL is malformed, expired, or revoked. Regenerate it in Discord and paste the new value into Tallwatch.
Alerts show a default bot name, not the one I picked
Alerts show a default bot name, not the one I picked
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.
Some alerts arrive much later than expected
Some alerts arrive much later than expected
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
| Property | Value |
|---|---|
| Channel kind | discord |
| Required config | webhook_url |
| Delivery | Immediate, no proactive rate limit; Discord enforces its own |
| Retry | Up to 3 inline attempts on 5xx, 429, network, or timeout, then failed |
| Outbound to | discord.com/api/webhooks |