Alerts & Notifications
SiteBrief notifies you instantly when something goes wrong — and again when it recovers. Here's every alert type and every delivery channel.
What triggers an alert
| Event | Alert sent |
|---|---|
| Site goes down | 🔴 Down alert — sent immediately (after confirmation if enabled) |
| Site recovers | 🟢 Recovery alert — sent when site responds normally again |
| SSL certificate expires in 30 days | ⚠️ SSL warning |
| SSL certificate expires in 14 days | 🚨 SSL critical |
| SSL certificate expires in 7 days | 🚨 SSL final warning |
| Domain expires in 30 days | ⚠️ Domain warning |
| Domain expires in 14 days | 🚨 Domain critical |
| Domain added to blacklist | 🚨 Blacklist alert (immediate) |
| Response time exceeds threshold | 🟡 Degraded alert |
Alert channels
| Channel | Plans | Configuration |
|---|---|---|
| All plans | Sent to your account email automatically | |
| Webhook | All plans | Add a webhook URL in site settings |
| Slack (Webhook) | All plans | Add Incoming Webhook URL in Integrations |
| Slack Bot | All plans | Add Bot Token + channel in Integrations |
| Discord | All plans | Add Discord webhook URL in Integrations |
| Telegram | All plans | Add Bot Token + Chat ID in Integrations |
| Microsoft Teams | All plans | Add Teams Workflows webhook URL in Integrations |
| PagerDuty | All plans | Add Routing Key (Events API v2) in Integrations |
| OpsGenie | All plans | Add API Key in Integrations |
| SMS (Twilio) | All plans | Add Twilio credentials in Integrations |
| Alert Escalation | All plans | Notify a secondary contact if site stays down |
Email alerts
Email alerts are sent to the email address registered on your SiteBrief account. Each alert email contains:
- Site name and URL
- What happened (down / recovered / SSL expiring)
- The HTTP status code or error message
- Timestamp of the event
- Direct link to the site detail page in SiteBrief
Recovery emails include the downtime duration — how long the site was unavailable.
Webhook alerts
Webhooks send a JSON payload via HTTP POST to any URL you configure in site settings. Use webhooks to integrate with any system: Slack, Discord, Telegram, your own backend, PagerDuty, or a custom alerting pipeline.
Webhook payload format:
{
"event": "site_down",
"site": {
"id": "uuid-here",
"name": "Acme Corp",
"url": "https://acmecorp.com",
"environment": "production"
},
"check": {
"status": "down",
"status_code": 503,
"response_time_ms": null,
"error": "Service Unavailable",
"checked_at": "2026-05-13T14:32:00Z"
}
}Event types in the payload:
| event value | When it fires |
|---|---|
| "site_down" | Site fails a check |
| "site_recovered" | Site comes back up after being down |
| "ssl_expiring" | SSL cert expiry warning (30/14/7 days) |
| "domain_expiring" | Domain expiry warning (30/14/7 days) |
| "blacklist_listed" | Domain added to a blacklist |
Setting up Slack
Option A — Slack Webhook (simple, no Slack app required):
- Go to api.slack.com/apps → Create New App → From Scratch
- Enable "Incoming Webhooks" and click "Add New Webhook to Workspace"
- Choose a channel and copy the
https://hooks.slack.com/services/...URL - Paste it into Integrations → Slack (Webhook)
Option B — Slack Bot (recommended, pick any channel dynamically):
- Go to api.slack.com/apps → Create New App → add
chat:writeBot Token Scope - Install to workspace and copy the
xoxb-...Bot Token - Run
/invite @YourBotin the target channel - Add Bot Token + channel name in Integrations → Slack Bot
Setting up Microsoft Teams
SiteBrief uses the new Teams Workflows webhook with Adaptive Cards:
- In Teams, go to the channel → Workflows → "Post to a channel when a webhook request is received"
- Complete the setup and copy the generated URL
- Paste it into Integrations → Microsoft Teams
Alert Escalation
If a site stays down and you need to notify a secondary contact (e.g. a manager or on-call engineer), configure Alert Escalation in Integrations:
- Set a secondary email to notify
- Set escalate after N minutes of continuous downtime
The escalation fires once per downtime event — you won't get spammed.
Alert fatigue — what NOT to do
- Don't add the same webhook URL to 20+ sites — you'll get flooded during a hosting outage affecting multiple clients
- Don't use personal phone SMS for non-critical staging sites
- Do use dual confirmation on sites that occasionally have brief blips
- Do set a maintenance pause before planned downtime windows