webhook-subscriptions

You can trigger agent workflows automatically by creating webhook subscriptions that connect external events from GitHub, Stripe, or GitLab to Hermes. The gateway validates incoming payloads using auto-generated HMAC secrets and starts the runs when events occur.

The best way to secure webhook deliveries is by using per-subscription HMAC secrets. This skill auto-generates secure secrets and validates request signatures for incoming payloads, ensuring that only verified external events trigger your automated workflows.

Yes, you need gateway availability to process external webhook events. The gateway is required to listen for incoming requests, validate their signatures, and trigger the corresponding Hermes agent runs automatically when events occur.

Hermes stores webhook subscriptions locally under the ~/.hermes/webhook_subscriptions.json file. This persistence allows the gateway to automatically reload your configurations and recover subscriptions seamlessly after an offline period or restart.

Yes, you can use webhook integrations to connect IoT services to Hermes. The skill creates dynamic webhook subscriptions that consume events from IoT devices, CI/CD pipelines, and other external platforms to trigger agent workflows automatically.

If external webhook events are not triggering Hermes runs, verify that the gateway is available and running. Also ensure the external service is sending the correct HMAC signature in the payload header so the subscription can successfully validate the request.