Uptime Kuma: push notifications with a real alarm sound
July 14, 2026 · 4 min read
Uptime Kuma is the homelab favorite for monitoring – but its notification options either need accounts and tokens or end up as easily-missed messages. A webhook notification pointed at Webhooky rings your phone with an actual alarm sound.
Setup in Uptime Kuma
- In the Webhooky app, create an endpoint called “Uptime”, pick an alarm sound (e.g.
buzzer) and enable Important. - In Uptime Kuma: Settings → Notifications → Setup Notification.
- Notification type: Webhook, Post URL: your Webhooky endpoint.
- Content type:
application/json→ Save, then enable the notification on your monitors.
That's already functional: every down/up event now triggers a push with your endpoint's configured title and text, and the full Kuma payload is kept in the app history if you enable store payload.
Nicer: put the monitor name in the notification
Recent Kuma versions offer a custom body for webhook notifications. Use it to map Kuma's variables onto Webhooky's fields:
{
"title": "🔴 {{ monitorJSON['name'] }}",
"message": "{{ msg }}",
"sound": "error_1"
}
Now the push itself says which monitor changed state. If your version doesn't have custom bodies, the default setup above still works – the details are one tap away in the history.
Tips
- Uptime Kuma sends both DOWN and UP events through the same notification. That's usually what you want – the UP push is the relief signal.
- Use a second, quieter endpoint for staging systems so only production sounds the alarm.
- Self-hosted Kuma only needs outbound HTTPS to
api.webhooky.app– no ports, no accounts.
Get Webhooky
Free for your first 100 notifications – set up your endpoint in two minutes.