Expanding web hooks...

[ny4i]

One of the ideas I would like to code up and test (a prior Q&A discussion I opened) is to extend the web hook capabilities. Right now to implement a webhook from HamAlert to Slack, I have a piece of glue code implemented on my ISP's web server to take the POST from HamAlert and do a subsequent libcURL call to the Slack web hook. This allows me to send a message when a spot is recorded with one of our club member's callsigns. Rather than have to require this glue, I would like to add some code to allow a drop-down to select the webhook type (Slack in my case but it could be Discord and others). This would require storing the access-key and URL of the webhook in a database somewhere. But those are fairly standard requirements of a webhook so the fields would be applicable to many other webhook types.

It would also be useful to have the ability to build the call so there could be a Slack and Discord template that builds the POST properly, but for a webhook we do not know about, being able to define the URL using $access-key or $SERVER would be useful.

Would that be a useful feature?

Tom
NY4I

[sonyccd]

I built a separate app to support discord but I think it makes more sense to contribute directly here
https://github.com/sonyccd/hamalert-discord