Keep running Uptime Kuma for your checks and status page, and let Edesy OnCall make the phone call. Add one Webhook notification pointing at an OnCall alert webhook URL: when a Kuma monitor goes down, OnCall calls your team in English or Hindi and escalates until someone presses 1. When it comes back up, the incident closes.
Webhook
Kuma notification type
0 / 1
Down / up status
1 incident
Per Kuma monitor
Free
For 3 monitors
Detected as Uptime Kuma automatically
Up closes the incident
Escalates until someone presses 1
How OnCall reads Kuma's webhook
| Item | Edesy OnCall |
|---|---|
| Notification | Notification Type: Webhook, Post URL: your alert webhook monitor's URL, Request Body: Preset - application/json |
| Detection | A payload with a heartbeat or monitor object is read as Uptime Kuma |
| Down | heartbeat.status 0 opens an incident, one per Kuma monitor |
| Up | heartbeat.status 1 closes it and sends back-up emails |
| Spoken text | The Kuma monitor's name; Kuma's message is shown in the incident |
| Test notification | Kuma's Test button is accepted and opens no incident |
| One OnCall monitor | Covers every Kuma monitor you enable the notification on |
About five minutes
In OnCall, add an Alert webhook monitor named "Uptime Kuma", attach an escalation policy and copy its URL.
In Uptime Kuma, open Settings, Notifications, Setup Notification and choose Webhook.
Set Post URL to the OnCall URL and Request Body to Preset - application/json. Save.
Turn the notification on for the Kuma monitors that deserve a phone call.
Pause and resume a test site, or stop a test service, to see the call and the incident timeline.
Replace the URL with the one from your OnCall alert webhook monitor.
Notification Type: Webhook Post URL: https://oncall.edesy.in/ingest/<token> Request Body: Preset - application/json
Kuma keeps doing the checks, including the check types OnCall doesn't have
OnCall adds phone calls in English or Hindi with press 1 to acknowledge
Escalation to a second and third person with wait times
Incident timeline with every call, key press and recovery
Your Kuma server must be able to reach oncall.edesy.in over HTTPS
If the Kuma server itself goes down, it can't send the alert: watch it with an OnCall HTTP check
All Kuma monitors on one notification share one escalation policy; add more OnCall monitors to split them
Monitor names are read aloud, so keep them short
Explore more comparisons, alternatives, and resources
Use cases
Tell us how many Kuma monitors you run and who should be called. We reply within one working day.
Create an alert webhook monitor on the Free plan and add it as a Kuma notification. Prices exclude 18% GST.