SiteBrief/Documentation

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

EventAlert 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
ℹ️
Note:Once a site is marked down, SiteBrief suppresses further "down" alerts for that event. You'll get one down alert and one recovery alert — not one alert per failed check.

Alert channels

ChannelPlansConfiguration
EmailAll plansSent to your account email automatically
WebhookAll plansAdd a webhook URL in site settings
Slack (Webhook)All plansAdd Incoming Webhook URL in Integrations
Slack BotAll plansAdd Bot Token + channel in Integrations
DiscordAll plansAdd Discord webhook URL in Integrations
TelegramAll plansAdd Bot Token + Chat ID in Integrations
Microsoft TeamsAll plansAdd Teams Workflows webhook URL in Integrations
PagerDutyAll plansAdd Routing Key (Events API v2) in Integrations
OpsGenieAll plansAdd API Key in Integrations
SMS (Twilio)All plansAdd Twilio credentials in Integrations
Alert EscalationAll plansNotify a secondary contact if site stays down
ℹ️
Note:All integrations are configured globally in Integrations and fire for all your monitored sites automatically.

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:

json
{
  "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 valueWhen 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:write Bot Token Scope
  • Install to workspace and copy the xoxb-... Bot Token
  • Run /invite @YourBot in the target channel
  • Add Bot Token + channel name in Integrations → Slack Bot
💡
Tip:Messages use Slack Block Kit — they'll look clean and structured in your channel.

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
ℹ️
Note:The old connector-based webhook (outlook.office.com/webhook/...) is deprecated by Microsoft. Use the Workflows URL instead.

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

Frequently asked questions

I'm getting too many alerts — how do I reduce noise?
Enable dual confirmation (requires 2 consecutive failed checks before alerting). Also set a maintenance pause before planned downtime. If a staging site doesn't need immediate alerting, remove its webhook URL and rely on email only.
I didn't get an alert even though the site was down for 10 minutes
Check your spam folder first. Then check the site's alert webhook URL and Integrations page. Also verify that monitoring isn't paused. Free plan checks every 2 minutes, Pro/Agency every 1 minute — if the site recovered within that window, only one failed check may have occurred.
Can I send alerts to multiple email addresses?
Currently alerts go to the account owner's email. Use a webhook to a service like Make (Integromat) or Zapier to fan out to multiple email addresses. Native multi-email support is planned.
Does SiteBrief retry webhook delivery if my server is down?
Yes. Failed webhook deliveries are retried 3 times with exponential backoff (1 min, 5 min, 15 min). If all retries fail, the alert is considered delivered (to prevent infinite loops if the monitoring server itself is the webhook target).