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.
Channels
| Channel | What it needs | Setup guide |
|---|---|---|
| Slack | An Incoming Webhook URL | Slack alerts |
| Discord | A channel webhook URL | Discord alerts |
| Telegram | A bot token and a Chat ID | Telegram alerts |
Where alerts are set up
- In the BooleanSMTP sidebar, click Alerts.
- Find Slack, Discord or Telegram in the provider list, then click Set up.
- Fill in the provider’s Settings fields; see that provider’s setup guide.
- Leave Send alerts on, click Send Test to check the connection, then click Save.
The provider row then shows Connected. From that row you can send another test, click Edit, pause alerts with the switch, or Disconnect the provider.
You can add one channel per provider. Each provider stays in the list after you connect it.
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.
- Connection health check failed: a connection failed its scheduled health check.
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.