Hi all, there's now two options for that which are:

📆

Both Zapier and DigitalOcean cost more than I want to spend on this, so I wanted to share a free solution I found that works better than using the email notification. Emails are ok but the formatting doesn't work well.

I set up with Pabbly (https://www.pabbly.com/connect/integrations/pushover/), which uses a webhook from updown.io, is easily configurable and is free at low volumes (100 notifications a month).

Thanks for your responses and for sharing you opinion @Steffen, I'll take it into account :) If others interested users have similar or different opinions, please do share them too!

First of all, thank you for giving this some thought!

I think I would switch to any official implementation by updown.io in order to remove third-parties like Pipedream from the equation (even if that would mean loosing the "priority" feature). Realiability is paramount.

I'm not sure that turning Pushover into some kind of poweruser feature makes more sense than simply adding another notification option (or even 5 or 10 other). If configuration is more difficult it could lead to more support requests. And if it feels brittle/fragile that could make users nervous about getting their notifications, too. Another option would make the settings page longer but wouldn't necessarily make it more complex or overwhelming because it's just one list of service names that I can skim in seconds. (Maybe you could collapse individual notification sections unless they have been configured if you are concerned about UI real estate?)

Still, if you are more comfortable implementing this as some kind of "official webhook proxy" than that would be fine for me.

Another intermediary solution I am thinking about is keeping a webhook proxy like you did, but making it "official", open-source, hosted by me in the updown infrastructure. The advantage would be that:

Not as good as a native integration of course but I can't do a native integration with every messaging service in the world. But maybe better than hosting your own?

The {description} would contain the summary string present in every webhook message under the attribute "description". For example "UP: https://updown.io/ since 18:04:04 (CET), after being down for 10 minutes, reason: 418 I'm a teapot" (see https://updown.io/api#webhooks for example from other webhook events). I think all other attributes present in the json could be supported as interpolations, though mostly those present for every event type would make sense (e.g. "event", "time", "description", "check.url", "check.token", ...). I'm not even sure this could work yet (haven't tested how pushover would react to having params in the URL + different unknown params in the POST body for example), so I'm asking to see if it's worth exploring.

Indeed setting the priority depending on the type of event would not be possible in this case, but it also wouldn't necessarily be possible if I implement a native integration. Because doing this by default may not please every users, and having even more options to configure integration specific settings depending on event type is not really on the table (not done for any integration ATM, no existing UI or storage options, etc).

So if this kind of customization is important, keeping this integration like you did in a small proxy would still be the best way IMO.

What would "{description}" contain and what other placeholders would there be? I have attached a screenshot of my current Updown.io -> Pipedream -> Pushover workflow such that you can see how I use it at the moment. Especially setting "priority" depending on whether something has gone down or come up seems useful.

(As a software developer I get your point that adding settings should be avoided when possible but IMHO not all settings are created equal. This would just be another option among the clearly labelled "Notifications" settings. It would not have any side-effects on other settings either. The Pushover API has been stable for years and the pricing is very attractive. All the workarounds using Pipedream/Zapier/DigitalOcean show that there is a real interest in getting Pushover working with updown.io.)

Another user suggested adding placeholder in updown's own webhooks URL (like the "description" attribute) in order to use the pushover API directly (see https://updown.uservoice.com/forums/177972/suggestions/47754338). This would be a bit hackish but would provide a direct connection without costing too much work and cluttering the UI with another integration. What do you guys think about this option? would it be enough for you use-cases? if not, why?

Having recently had email delivery issues and discovered PushOver.net, I agree with the initial idea it would be amazing to have a native integration in UpDown.io

It would be a game-changer, in my opinion.

Hi Michael

It likely will because I see it gaining popularity, but considering the alternatives way to connect it already: Zapier, the function by Marc, or even their Email gateway (https://support.pushover.net/i29-e-mailing-notifications-to-your-devices), this is not in the short-term roadmap.

You may want to try their Email gateway to avoid intermediaries, I'm not sure how the formatting will come out though.