The gap this fills: UptimeRobot doesn't ship an official ntfy app. If you want uptime or downtime alert to show up in ntfy the moment it happens, the usual options are a paid third-party bot, custom code, or routing everything through a $20–50/month automation platform just to move one webhook from one URL to another. ZestyGlue does exactly that one thing for $9/month.
What it looks like
ZestyGlue
UptimeRobot — Down
api.example.com
https://api.example.com/health
Connection timeout
A real UptimeRobot event, shown as ZestyGlue formats it for ntfy.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new UptimeRobot → ntfy connector. You'll get a unique webhook URL right away.
- Point UptimeRobot at it. Go to My Settings → Add Alert Contact → Webhook, choose "Send as JSON", and paste in your ZestyGlue webhook URL.
- Point ntfy at ZestyGlue. Pick any topic name — e.g.
https://ntfy.sh/your-secret-topic — enter it into ZestyGlue, and subscribe to that same topic in the ntfy app or web client.
Tip: UptimeRobot sends the same alert type on both the way down and the way back up (Down, then Up) — seeing both in your channel means you always know when an incident actually resolved, not just when it started.
Events you can forward
Up
Down
SSL Expiring
Questions
Does this work with UptimeRobot's free plan?
Yes — webhook alert contacts are available on UptimeRobot's free tier, not just paid plans.
Can I monitor multiple sites with one connector?
Yes — add the same ZestyGlue webhook URL as the alert contact on as many monitors as you like.
Do I need to self-host ntfy?
No, the free public ntfy.sh server works fine for most people — just pick an unguessable topic name.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on UptimeRobot's side — UptimeRobot never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.