webhook-subscriptions

Triggering agent runs from external webhook events requires creating subscriptions that map incoming JSON payloads to your runtime, allowing platforms like GitHub or Stripe to post events to a URL and activate agents.

A webhook subscription for automated agent activations is a gateway-managed configuration that validates HMAC signatures and dispatches runs by receiving JSON payloads from external services to connect them to your runtime.

Yes, the webhook gateway supports GitHub, GitLab, and Stripe integrations alongside CI/CD pipelines and IoT sensors, managing subscriptions and validating signatures for any service capable of posting JSON payloads to trigger runs.

Creating a webhook subscription listening for GitHub issues involves configuring a URL endpoint and mapping the incoming event payload to your agent, with the gateway validating the request signature using an auto-generated or custom HMAC secret before dispatching the run.

You need the Hermes webhook platform enabled to use webhook subscriptions, as it provides the required gateway infrastructure to manage subscriptions, validate HMAC signatures, and dispatch agent runs from external events.

Webhook signatures are validated to prevent payload tampering by using an auto-generated or custom HMAC secret for each subscription, with the gateway checking the signature of incoming JSON payloads before dispatching agent runs.