EventBar
Guides · Uptime Kuma
Get a Mac notification when Uptime Kuma marks a monitor down
Uptime Kuma's webhook notification type posts JSON on every status change. Route it to EventBar and a down site is a notification you can't miss, with a count of incidents over the month.
Needs: the free EventBar app on your Mac, an EventBar account, and a Uptime Kuma account with permission to add webhooks. About five minutes. Generic JSON.
Steps
- Create the webhook URL. In the EventBar dashboard, open the Webhooks tab, pick the group this belongs to (one group per site or app is the usual shape), choose the provider Generic JSON, name it, and press Create. Copy the URL; it stays visible and can be rotated any time.
- Paste it into Uptime Kuma. In Uptime Kuma: Settings, then Notifications, then Setup Notification, type Webhook, Post URL your hook URL, request body Preset - application/json. Create the EventBar hook as Generic JSON with default type
monitor. Attach the notification to the monitors you care about. - Trigger one. Most services offer a test delivery; otherwise do the real thing once. It shows up in the dashboard's Events tab within a second and in the menu bar, as an undefined type named after the event. That first one is your proof the wiring works.
- Make it read well. Press Define on the new type and give it a title and a body template. Fields come from the payload, nested ones with dots. The table below is a starting point.
What you'll see
| Type | Title | Body template |
|---|---|---|
monitor | Status change | {msg} |
Every type has its own switch in the menu bar, so a noisy one can be quiet on this Mac and still counted. Counts cover the last hour, 24 hours, 7 days, 30 days and all time.
Worth knowing
{msg}is Uptime Kuma's own one-line summary, which already names the monitor and whether it is up or down.{monitor.name}and{heartbeat.status}are there if you want to compose your own.- Link template
{monitor.url}opens the site that went down.
The full contract, including how each preset reads a payload and what the answers mean, is in the API docs. Something about Uptime Kuma's payload changed? Tell us and we'll fix the guide.