Skip to main content
Alert channels define where Larm sends notifications when a monitor goes down or recovers. Each monitor can be linked to one or more channels. Larm sends alerts for these events:
  • Monitor down — a monitor has been confirmed down
  • Monitor recovered — a monitor is back up
  • Certificate expiring — an SSL certificate is nearing expiry
  • Test — a manual test alert sent from the dashboard

​
Slack

Posts a formatted message to a Slack channel via an incoming webhook.

​
Discord

Posts an embed message to a Discord channel via webhook.

​
Email

Sends an HTML email to one or more recipients.

​
Webhook

POSTs a JSON payload to any HTTPS URL. Use this to integrate with services Larm doesn’t have a native adapter for. See Webhooks for payload format, template variables, and signature verification.

​
PagerDuty

Triggers and resolves incidents via the PagerDuty Events API v2. When a monitor goes down, Larm triggers a PagerDuty incident. When it recovers, Larm automatically resolves the incident using a stable dedup key.

​
Microsoft Teams

Posts an Adaptive Card message to a Teams channel. Supports both legacy Office 365 Connector and Power Automate Workflow webhooks.

​
Grafana IRM

Creates and resolves alerts in Grafana OnCall via the Formatted Webhook integration. When a monitor goes down, Larm creates an alert in Grafana OnCall. When it recovers, the alert is automatically resolved using a stable dedup key.

​
ilert

Creates and resolves alerts via the ilert Events API. ilert is an EU-native incident management platform based in Cologne, Germany. When a monitor goes down, Larm creates a HIGH-priority alert in ilert. When it recovers, the alert is automatically resolved using a stable dedup key. Certificate expiry and test alerts are created with LOW priority.

​
incident.io

Creates and resolves alerts via incident.io’s HTTP Alert Source API. When a monitor goes down, Larm fires an alert in incident.io. When it recovers, the alert is automatically resolved using a stable dedup key.

​
Mattermost

Posts a formatted message to a Mattermost channel via an incoming webhook.

​
Pushover

Sends push notifications to your devices via Pushover.

​
ntfy

Sends notifications via ntfy, a simple pub/sub notification service. Works with the public ntfy.sh instance or your own self-hosted server.

​
Telegram

Sends messages to a Telegram chat via the Bot API. You provide your own bot (created via @BotFather) and a chat ID. To find your chat ID, send a message to your bot and visit https://api.telegram.org/bot<token>/getUpdates.

​
SMS

SMS alerts are available on Pro and Business plans.
Sends a text message to a verified phone number. When you add an SMS channel, the phone number must be verified via a confirmation code. SMS alerts are metered: Pro plans include 125 messages per month, Business includes 500 per month. Additional hourly and daily rate limits apply to prevent burst costs from flapping monitors.

​
Retries and failure handling

Alert delivery is attempted up to 3 times with exponential backoff. If a channel returns a permanent error (401, 403, or 404), Larm disables the channel automatically and notifies the organization owner by email. You can re-enable it from the dashboard after fixing the configuration.