Congratulations on the thriving open-source project you’ve managed to build up! I’m happy to be part of this great community!
Have you considered using websockets as a Trigger?
I have this case where we would like to send triggers to n8n without having to manually define the URL of each webhook (each having a different URL makes them usable in one place), but rather set up more general Triggers to listen for certain events being sent to them. This way, we would be able to trigger only one endpoint from the server, which would then propagate to all the n8n workflows subscribed and configured accordingly.
As options, I believe that the host (ws url), the channel to subscribe to and the event to bind would do.