Notification Channels

Channels define where notifications are sent. Each team can have multiple channels of different types, allowing you to route alerts to the right people and tools.

Email

The default notification channel. Sends formatted HTML emails with incident details, monitor information, and direct links to the dashboard.

• Sends to any email address (does not need to be a team member).
• Bilingual templates -- sent in the recipient's configured language (English or German).
• Includes monitor name, failure cause, timestamps, and a link to the incident.

Slack

Integrate with Slack using an incoming webhook URL.

1. Create an incoming webhook in your Slack workspace.
2. Add a Slack notification channel in Hoppla and paste the webhook URL.
3. Notifications are sent as rich messages with monitor details, status indicators, and links.

Microsoft Teams

Integrate with Microsoft Teams using a webhook URL.

1. Create a webhook URL for your Teams channel and paste it into a Microsoft Teams notification channel in Hoppla.
2. Notifications appear as adaptive cards with incident information.

Incoming webhook connectors are being retired

Microsoft is deprecating the legacy Office 365 "incoming webhook connector". For new channels, generate the webhook URL from a Teams Workflows connector (Power Automate) instead -- the resulting URL works the same way in Hoppla.

PagerDuty

Integrate with PagerDuty via the Events API v2 for on-call escalation.

1. Create a service in PagerDuty and add an Events API v2 integration.
2. Copy the integration key.
3. Add a PagerDuty notification channel in Hoppla and paste the integration key.

Hoppla automatically creates PagerDuty incidents when monitors fail and resolves them when monitors recover.

Discord

Integrate with Discord using a webhook URL.

1. In your Discord server, go to channel settings and create a webhook under Integrations.
2. Copy the webhook URL.
3. Add a Discord notification channel in Hoppla and paste the webhook URL.
4. Notifications are sent as rich embeds with monitor details and status indicators.

Telegram

Integrate with Telegram using a bot.

1. Create a bot via @BotFather and copy the bot token.
2. Add the bot to your group chat or start a direct conversation with it.
3. Get the chat ID (send a message to the bot and check the Telegram API for the chat ID).
4. Add a Telegram notification channel in Hoppla with the bot token and chat ID.

Webhook

Send JSON payloads to any URL for custom integrations. Webhooks include an HMAC-SHA256 signature header for payload verification.

The payload is a flat JSON object -- there are no nested monitor/incident objects. Keys are sorted alphabetically. Example webhook payload:

{
  "check_type": "uptime",
  "event": "incident.created",
  "incident_id": "uuid",
  "monitor_id": "uuid",
  "monitor_name": "example.com",
  "monitor_url": "https://example.com",
  "severity": "critical",
  "status": "down",
  "timestamp": "2026-03-04T12:00:00Z",
  "title": "HTTP 503 Service Unavailable"
}

The exact keys depend on the event type -- for example, dns.records_changed payloads also include zone, nameservers, and changes.

The signature is sent in X-Webhook-Signature, computed as HMAC-SHA256(secret, raw_request_body) and hex-encoded. The same value is repeated in the legacy X-Hoppla-Signature header for integrations built before September 2026; use the neutral name in new code. The secret is the value you enter in the channel's HMAC Secret field (optional).

The custom headers and HTTP method fields are accepted by the API but are not currently applied — every delivery is a POST with Content-Type: application/json plus the signature headers.

Full contract, verification snippets and the complete event catalogue: Webhooks.

Managing Channels

All notification channels are managed from Settings > Notification Channels in the dashboard.

• Create -- Click "Add Channel", select the type, and configure the connection details.
• Test -- After creating a channel, click "Send Test" to verify it works. A test notification is sent immediately.
• Edit -- Update channel configuration at any time. Existing notification rules using the channel are unaffected.
• Delete -- Removing a channel also removes it from any notification rules that reference it.