Could you please support Pushover besides Slack?
https://pushover.net
It’s easy to implement and works perfectly well.
Many thanks
Tobias
@TobiWahnKenobi I have got this working using a little bit of node-red code to receive the web hook and transform the message
I talked to the team while at Engage about writing this up…
It can probably be done with a Connect flow too, now we all get it free, am going to test that before I write up.
Thanks. I just I think this is a bandaid as using the API directly is really easy. I get that we can push to slack and then push from there to something else but that is quite inefficient.
I understand that the team cannot support all Push Clients. I just think since Pushover is mostly free it is a nice addon with many possible applications.
I also use Prowl (old school also free) and same thing is true, the webhook output form Otto needs transforming somewhere to then match up with that API (although API is a bit of an overstatement as it has a single method)
I did use prowl but since we have colleagues who use android it is no longer feasible. So we switched to Pushover. Which works nicely, looks better, has a desktop “app” and can use different images for different channels.
Ahhh, sorry! Now I get it! Never noticed the Webhook section under Notifications.
So I had a look at the Webhook route and I cannot use it for pushover without an intermediate since I have to supply the token as part of the body.
If the weebhook functionality could gain support for a more variable structure where we could specify HOW the body should be set up (with the message as a variable part) and perhaps also use the message from otto as a variable we can post into a header? That would make it much more versatile without requiring an additional middleware/solution.
But if you can support Pushover native that would be wonderful as well 