Yellow-Dog-Man
Native Webhook Support
Is your feature request related to a problem? Please describe.
It would be cool to have a native built-in solution for handling webhook signals (incoming and outgoing). This would open Resonite to more opportunities with using APIs that can't use the current protocols we have at this moment. Outgoing signals for webhooks do require POST String and it works ok (if one knows what to do), but there is no way to receive a webhook signal directly into Resonite.
Having webhooks would allow for the following examples:
- Direct discord messaging when sending out from Resonite and into a channel
- Receiving incoming API signals from another external program, application, or web service (such as creators using Kofi's Webhook API and having a listener webhook on Resonite's side to send triggered pulses and data)
- IFTTT integration utilizing webhooks
- Homelab / IoT / and many other projects that have listeners and senders for this functionality.
Describe the solution you'd like
A set of nodes and/or components that can handle webhook integration and data transmission bidirectionally.
Describe alternatives you've considered
The only other way is hosting your own server for sending/receiving requests (including getting hardware, writing in a completely different coding language, etc), creating your own API for listening (using php, python, or similar), and handling that data manually for Resonite to then use (obtaining, parsing, and utilizing it). This alone would be more work on the user's end, when a built-in solution would be preferred and easier for the user to use.
Additional Context
N/A
Requesters
- AmasterAmaster
Are you looking for essentially being able to host a HTTP server through the nodes on Resonite and be able to receive and process any requests?
I'm not sure how practical this would be, because that usually needs hosting on a static IP with a specific port that needs to be exposed to the internet and sessions in Resonite tend to be more transient.
Are you looking for essentially being able to host a HTTP server through the nodes on Resonite and be able to receive and process any requests?
Kinda yes, but different than how websockets do it (as that sounds similar). and I know that not everything can use similar standards (one thing uses headers, another uses sockets, and some are webhook only). Having a listener would be that one thing Resonite is missing.
because that usually needs hosting on a static IP with a specific port that needs to be exposed to the internet
Understandable, having static IPs would be a pain to juggle around, another idea would be specific Resonite website domains dedicated for it, that could be setup for these webhook signals, but that is something you all would know what is best to handle that.
sessions in Resonite tend to be more transient.
I was also thinking more how headlesses can be up for longer periods of time and can be listening while they are up, but I guess transient is subjective in that case.