Discord alerts

BooleanSMTP posts a Discord message the moment an outgoing email finally fails to send. Setup uses a Discord webhook you create yourself — BooleanSMTP only ever sees the webhook URL you paste in. There is no bot to create and no ID to look up: the webhook URL already identifies the destination channel.

Create a Discord webhook

1. In Discord, open the server and channel you want alerts posted into.
2. Open that channel’s settings and go to Integrations → Webhooks.
3. Click New Webhook, give it a name (for example “BooleanSMTP Alerts”), and confirm the target channel.
4. Click Copy Webhook URL. It looks like https://discord.com/api/webhooks/123456789012345678/AbCdEfGh.... Anyone with this URL can post messages into that channel, so keep it private.

Connect Discord in BooleanSMTP

1. In the BooleanSMTP sidebar, click Alerts.
2. Under Available Providers, click the Discord card.
3. In Friendly Label, enter a name for this channel (for example “Ops Discord”).
4. In Webhook URL, paste the URL you copied.
5. Webhook display name is optional. It changes the sender name Discord shows on each alert message — it does not change which channel the alert posts to. Leave it blank to use “BooleanSMTP”.
6. Leave This webhook URL is proxied through a third-party relay unchecked, unless you are intentionally routing the webhook through your own proxy instead of pointing straight at Discord. Checking it accepts any HTTPS URL instead of just Discord’s own domain.

Send a test alert

1. Toggle Live Channel on. BooleanSMTP does not send real alerts through a channel that is off.
2. Click Send Test. BooleanSMTP posts a real message to Discord using the values currently in the form.
3. Click Activate Channel to save.

A failed test shows Discord’s own error text, not just “failed” — see below for what the common ones mean.

Common errors

“Discord Webhook URL is required.” — the Webhook URL field is empty.

“This does not look like a Discord webhook URL.” — the URL doesn’t match Discord’s webhook shape. Check you copied the full URL from Discord’s Copy Webhook URL button, not a different service’s webhook — or check This webhook URL is proxied through a third-party relay if you’re intentionally using a proxy.

“Unknown Webhook” — the webhook was deleted or regenerated in Discord’s channel settings. Create a new webhook and update the URL here.

A rate-limit message (“You are being rate limited”) — Discord is rate-limiting this webhook. This is rare for normal alert volume; if you see it often, several sites are likely sharing one webhook — create a separate webhook per site.

Send Test worked, but no alerts arrive — confirm Live Channel is on and the channel was saved with Activate Channel (or Update Channel), not left unsaved in the form.

Alerts arrive in the wrong channel — the webhook URL fixes the destination channel in Discord; there’s no separate channel selector in BooleanSMTP. Create a new webhook against the right channel and update the URL here.

See also: Alerts, Slack alerts, Telegram alerts.