Alerts & Notifications
    Feature Guide

    Setting Up Alerts

    Configure 11 notification channels — email, push, chat, on-call, and automation tools.

    Updated 2026-06-11
    2 min read
    alerts
    notifications
    email

    Quick answer

    How to set up website downtime alerts?

    Enable email by default, then add Slack, SMS, Teams, Discord, PagerDuty or webhooks — set an escalation policy so a secondary contact is paged if the primary doesn't ack in N minutes.

    Setting Up Alerts#

    LemWatch ships 11 notification channels. Configure global defaults in Settings → Notifications, then override per site if needed. See Default vs per-site channels for the precedence rules.

    Email & Push (All Plans)#

  1. Email — Enabled by default. Customise event types, digest frequency, and quiet hours in Settings → Notifications.
  2. Browser Push — Instant OS notifications even when LemWatch isn't open. See Browser Push Notifications.
  3. Chat & Team Channels (Pro+)#

  4. Slack — Incoming webhook with rich attachments. Setup
  5. Microsoft Teams — Workflows (Adaptive Cards) or legacy O365 connector. Setup
  6. Discord — Colour-coded embeds. Setup
  7. Telegram — Your own bot via @BotFather. Setup
  8. Google Chat — Space webhook. Setup
  9. Mattermost — Slack-compatible incoming webhook. Setup
  10. Rocket.Chat — Incoming integration. Setup
  11. ntfy.sh — Push to phone or desktop, self-hosted friendly. Setup
  12. On-call & Automation#

  13. PagerDuty — Events API v2 with auto-resolve. Setup (Agency)
  14. Generic Webhook — JSON POST to any HTTPS endpoint. Setup
  15. Zapier / Make / n8n / IFTTT / Pipedream — Route alerts into any of 5,000+ apps through the Mattermost field. Recipes
  16. RSS — Subscribe to alerts as a feed. Setup
  17. Alert Severity#

  18. Critical 🔴 — Site down, security vulnerability, SSL expired (never suppressed)
  19. Warning 🟡 — Performance degradation, approaching limits
  20. Info 🔵 — SSL renewal, check completed, maintenance ended
  21. Best Practices#

  22. Set up at least two channels (e.g., email + Slack) for redundancy.
  23. Use quiet hours to prevent alert fatigue.
  24. Configure consecutive failure thresholds to avoid false positives.
  25. Route critical alerts to PagerDuty for on-call teams (Agency).
  26. Use the Send test button under each channel to verify before going live.
  27. Was this article helpful?

    Related Articles

    Notification Channels Overview

    Tour of all 11 channels with links to the full setup walkthrough.

    Default vs Per-Site Channels

    How LemWatch picks which channel and recipient to use for each alert.

    Slack Integration

    Connect LemWatch to Slack and route uptime, SSL, and performance alerts into any channel with per-severity filtering and mentions.

    Discord Integration

    Send LemWatch monitoring alerts to any Discord server via webhook with role pings, embeds, and channel-level routing controls.

    Microsoft Teams Integration

    Send monitoring alerts to your Microsoft Teams channels.

    Telegram Integration

    Receive LemWatch downtime, SSL, and performance alerts as Telegram messages via a bot token and chat ID configured per site.

    Google Chat Integration

    Send LemWatch alerts to a Google Chat space via incoming webhook.

    Mattermost Integration

    Connect LemWatch alerts to a Mattermost channel via incoming webhook.

    Rocket.Chat Integration

    Send LemWatch alerts to a Rocket.Chat channel via incoming integration.

    ntfy.sh Integration

    Push LemWatch alerts to your phone or desktop via ntfy topics.

    PagerDuty Integration

    Route critical alerts to PagerDuty for on-call incident management.

    Custom Webhook Integration

    Send alert data to any HTTP endpoint via custom webhooks. Slack and Discord URLs are auto-routed when used in escalation steps.

    Automation Recipes (Zapier, Make, n8n, IFTTT, Pipedream)

    Pipe LemWatch alerts into any of 5,000+ apps via your favourite automation tool.

    Browser Push Notifications

    Receive instant browser alerts for critical events.

    Quiet Hours & Alert Frequency

    Suppress non-critical alerts during off-hours. Held alerts still appear in the inbox with a scheduled delivery time.