# Alerts

> What BooleanSMTP's Slack, Discord and Telegram alerts are, what triggers one, and where to connect a channel.

BooleanSMTP can post an alert to **Slack**, **Discord** or **Telegram** when something is wrong with your outgoing email —
so you find out from a message in a channel you already watch, instead of from a customer telling you their password reset
never arrived. There is no email alert channel: if email itself is the thing that's broken, an alert that also depends on
email would not reach you.

![The Alerts screen: the Telegram, Slack and Discord provider cards, and a connected channel listed below.](../../../assets/screenshots/alerts.webp)

## Channels

| Channel | What it needs | Setup guide |
| --- | --- | --- |
| **Slack** | An Incoming Webhook URL | [Slack alerts](/alerts/slack/) |
| **Discord** | A channel webhook URL | [Discord alerts](/alerts/discord/) |
| **Telegram** | A bot token and a Chat ID | [Telegram alerts](/alerts/telegram/) |

## Where alerts are set up

1. In the BooleanSMTP sidebar, click **Alerts**.
2. Under **Available Providers**, click the card for **Slack**, **Discord** or **Telegram**.
3. Fill in the **Friendly Label** (a name to recognize this channel by later) and the fields under **Connection Payload** —
   these are different for each provider; see that provider's setup guide.
4. Toggle **Live Channel** on, click **Send Test** to check it works, then click **Activate Channel** to save it.

Channels you've added are listed under **Connected Channels**, where you can send another test, edit a channel, toggle it
on or off, or delete it.

You can add **one channel per provider**. Once a provider has a channel, its card no longer appears under
**Available Providers**.

## What triggers an alert

- **Email delivery failure**: an outgoing email has exhausted its retries and its fallback connection, and is truly
  undeliverable. This does not fire on the first transient error — only once BooleanSMTP has given up on the message.
- **OAuth sign-in expired**: a Google Workspace or Microsoft Outlook connection's OAuth token failed to refresh and needs you to sign
  in again.

Repeated alerts of the same type and connection are throttled, so a burst of failures doesn't flood your channel with one
message per email.