Uptime Kuma integration

Turn Uptime Kuma downtime into phone calls, Telegram and escalation

Point any Uptime Kuma monitor's webhook notification at WardenPoint. Downtime fires an escalation chain; the recovery notification posts a Resolved notice. Zero code.

Start free View API examples
Setup
Per monitor
Recovery
Resolved ping
Channels
8

Anatomy of a Kuma downtime

LIVE
Uptime Kuma → notification
payments-api unreachable for 60s
WardenPoint
escalate · ack · resolved notice
Telegram
Voice call
Email

Setup

Three clicks per monitor

Uptime Kuma stores notifications per monitor. Add WardenPoint once, then attach it to whichever monitors should escalate.

  1. 1Step 1

    Add WardenPoint as a notification

    Settings → Notifications → Setup Notification. Pick 'Webhook' as the type. Name it WardenPoint.

    $ Settings › Notifications › + Setup
  2. 2Step 2

    Paste the URL and auth header

    Paste your WardenPoint URL into Post URL (request type POST). Under Additional Headers add Authorization: Bearer <your secret>, and keep the body as application/json.

    $ Post URL › https://wardenpoint.com/api/v1/integrations/alerts/…
  3. 3Step 3

    Attach to monitors

    On each monitor you want to escalate, open Edit → Notifications → tick 'WardenPoint'. Recovery notifications fire automatically.

    $ Monitor › Edit › Notifications

Wire format

What Uptime Kuma posts on downtime

Kuma sends monitor metadata plus a heartbeat object describing the failure. WardenPoint extracts the monitor name, URL and up/down status.

Kuma → WardenPoint
kuma-webhook.jsonJSON
{
"monitor": {
"name": "payments-api",
"url": "https://api.example.com/health",
"type": "http"
},
"heartbeat": {
"status": 0,
"msg": "Connection timeout after 10s",
"time": "2026-05-17 13:42:18"
}
}
WardenPoint fan-out
WardenPoint response202
{
"status": "queued",
"notification_uuid": "notif_8h2k7yQrxJp",
"channels_planned": [
"telegram_voice",
"voice_call",
"email"
],
"escalation_chain_id": "esc_4j2k9bMcvL"
}

Routing recipes

Three patterns for uptime workflows

Run different monitor groups through separate WardenPoint integrations, each wired to its own escalation chain.

Tier

Tier-1 services → call

Create a dedicated WardenPoint integration for tier-1 monitors (payments, auth, checkout) whose recipient group hits voice and Telegram first, then attach it to just those monitors. Tier-2 monitors point at a second integration that goes to email.

match
tier-1 monitors
→ route
→ voice + Telegram
Environment

Production-only escalation

Run prod and staging monitors through separate WardenPoint integrations. Attach the full-chain integration to production monitors; send staging downtimes to an email-only one.

match
prod monitors
→ route
→ full chain
Recovery

Recovery posts a Resolved notice

Uptime Kuma fires a recovery notification automatically when the monitor comes back. WardenPoint marks the alert resolved and posts a Resolved notice to your chain.

match
heartbeat.status: 1 (up)
→ route
→ Resolved notice

Uptime Kuma FAQ

Common Uptime Kuma integration questions

Yes. By default, Kuma fires a notification both on downtime and on recovery. WardenPoint reads the heartbeat.status value and, on recovery, marks the alert resolved and posts a Resolved notice. An escalation already in flight is stopped by acknowledging.
Free plan

Make Kuma downtimes harder to miss

Connect one monitor, knock down its endpoint and watch the escalation chain run end to end.

Start free Back to integrations
  • Per-monitor wiring
  • Recovery posts a Resolved notice
  • No flap alerts