Tallwatch sends an embed-style incident message to your Discord channel via a Discord webhook URL. Setup takes about two minutes.Documentation Index
Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt
Use this file to discover all available pages before exploring further.
Before you start
- You must have Manage Webhooks permission on the target Discord server.
- Pick the channel that should receive alerts. A dedicated channel like
#incidentsis cleaner than your general channel.
Step 1: Create a webhook in Discord
Open channel settings
Right-click the Discord channel that should receive alerts, then click Edit Channel.
Name and configure the webhook
Give it a recognisable name like
Tallwatch. Optionally upload an avatar — the alerts will appear as messages from this identity in your server.Step 2: Add the channel in Tallwatch
Pick Discord
Select the Discord kind. Name the channel for the audience:
Discord #incidents or OSS contributors.What the alert looks like
A single Discord embed per incident event with:- The monitor name as the embed title
- An embed colour matching the event severity (red opened, green resolved)
- A short description plus inline fields for failing regions, duration, and the consensus rule
- A link back to the incident detail page in Tallwatch
Troubleshooting
Test alert sent but nothing arrived
Test alert sent but nothing arrived
The webhook may have been deleted on the Discord side. Discord silently drops messages to deleted webhooks. Recreate the webhook and update the URL in Tallwatch.The channel might also be in a server you no longer have access to. Re-check the URL still works by looking it up under the channel’s integration settings.
`webhook_invalid` error in the dispatch history
`webhook_invalid` error in the dispatch history
The URL is malformed, expired, or revoked. Regenerate it in Discord and paste the new value into Tallwatch.
Alerts show as a default Discord bot, not the name I picked
Alerts show as a default Discord bot, not the name I picked
The webhook still works; the display name attaches at webhook-creation time. To rename, edit the webhook in Discord — Tallwatch does not override the name on send.
Some alerts arrive much later than expected
Some alerts arrive much later than expected
Channel rate limit. Tallwatch caps each channel at one alert per 30 seconds and queues excess. The queued messages deliver after the window opens. Split monitors across multiple Discord channels if you need higher throughput on a noisy hour.
Reference
| Property | Value |
|---|---|
| Channel kind | discord |
| Required config | webhook_url |
| Send rate limit | 1 per 30 s per channel (queued, not dropped) |
| Retry policy | Up to 3 attempts on 5xx, then queued for the next 30-s slot |
| Outbound to | discord.com/api/webhooks |