webhook-subscriptions

To trigger an agent run from a GitHub webhook, configure an external service to send an HTTP POST payload to a secure subscription endpoint, which validates the request using a generated HMAC secret and starts the run.

Yes, Stripe can send HTTP POST payloads to a subscription endpoint to trigger automated actions. Subscriptions support multiple event sources including Stripe, validating incoming requests with per-subscription HMAC secrets.

Webhook subscription security validates incoming events by generating a unique HMAC secret for each subscription and using it to authenticate incoming HTTP POST requests before triggering any agent runs.

The best way to persist webhook subscriptions for CI/CD pipelines is storing them in your local configuration, allowing you to reuse secure endpoints that trigger agent runs from CI/CD pipeline events.

No external dependencies are required to configure event-driven subscriptions. The system persists subscriptions locally and generates the necessary HMAC secrets internally to validate incoming HTTP POST payloads from external services.

External services that work with custom webhook payloads include GitHub, GitLab, Stripe, and CI/CD pipelines. Any service capable of sending HTTP POST requests to a secure endpoint can trigger an agent run.