hermes - 💡(How to fix) Fix [Feature]: Support for generic webhooks [2 comments, 2 participants]

Problem or Use Case

Currenty, webhooks are specific to the format GitHub is using, thus you can filter for event types and other stuff within the payload GitHub uses in it's webhook payloads.

However, I have many use cases, where I want to wake up the agent with a generic (maybe even self-crafted, or emitted from arbitrary other software) webhook request.

Proposed Solution

Implement a new "generic webhooks" channel. The easiest solution would be to be able to specify the prompt directly as a parameter (e.g. a field prompt within a JSON POST body), alongside other paramerts (model to be used, deliver options like with cron, etc.). Like with the current GitHub webhooks, this promt should create a new session, where the prompt will be processed. There should be a delivery option to a main channel.

Another option is to accept generic payloads, and let the user specify a script to transform the payload into a promt (like OpenClaws mapped hooks).

Alternatives Considered

You could just use the GitHub webhooks and build a "webhook adapter" that emits webhooks in the GitHub format. While this is possible, it is hacky and intruduces a custom component, users need to maintain themselfs.

Feature Type

Other

Scope

Medium (few files, < 300 lines)

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)