Alerts & Notifications

    Escalation Step Channels

    How each step in an escalation policy maps to a channel — email, Slack, Discord, generic webhook — based on the Recipient value.

    Updated 2026-06-15
    2 min read
    escalation
    channels
    slack

    Escalation Step Channels#

    Each step in an escalation policy has a Channel dropdown and a Recipient field. The two together decide who gets pinged.

    Channel: Email#

  1. Recipient: any email address (e.g. oncall@yourcompany.com)
  2. LemWatch sends a single addressed email via the standard transactional pipeline
  3. Honours per-site notification email overrides if you leave the field blank

    4. Channel: Slack#

  4. Recipient: a Slack incoming-webhook URL (https://hooks.slack.com/services/...)
  5. We post a Slack-formatted message with the same attachment block used by your default Slack channel
  6. If you paste a Slack URL into any step regardless of the dropdown, we route it to Slack automatically

    7. Channel: Discord#

  7. Recipient: a Discord webhook URL (https://discord.com/api/webhooks/...)
  8. We post a Discord-formatted message with severity-coloured embeds
  9. Discord URLs are auto-detected the same way

    10. Channel: Webhook#

  10. Recipient: any other https:// URL
  11. We POST the same JSON payload documented in Custom Webhook Integration
  12. Use this for PagerDuty Events API, Opsgenie, internal incident tooling, Zapier catch hooks, etc.

    13. Why auto-routing matters#

    Before, only email recipients reached the recipient field correctly — Slack/Discord/webhook step URLs were silently dropped. The engine now inspects the URL on every step and routes it to the matching downstream channel.

    Tips#

  13. One policy can mix all four channel types across its steps
  14. Wait between steps so the previous recipient has a chance to acknowledge
  15. For high-noise alerts, put a digest-friendly channel (email) first and a louder one (webhook → PagerDuty) later
    16. Was this article helpful?

    Previous

    Escalation Policies

    Next

    Alert Digest Mode

    Related Articles

    Escalation Policies

    Build multi-step escalation policies so alerts reach the right person, in the right channel, at the right time.

    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.

    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.

    Back to Help Center