webhook-subscriptions

You can trigger agent runs automatically by creating webhook subscriptions that map incoming event payloads to agent activation. Point your external service's webhook to the returned URL to start runs on GitHub issues or Stripe payment events automatically.

You format incoming JSON payloads into instructions by using prompt templates with payload field interpolation. Dot.notation allows you to extract specific fields from the event data, translating each event into an actionable instruction for the agent.

Yes, you can deliver responses to multiple targets like Telegram, Discord, or GitHub comments. The subscription management system supports routing processed results to these platforms after an event triggers an agent run.

To secure event webhooks, the system applies HMAC signature handling to verify incoming payloads. This ensures that external event sources triggering agent runs are authenticated and prevents unauthorized activation.

You manage and test event-driven webhook subscriptions using built-in subscription management commands. You can create, list, remove, and test routes to ensure your event filtering and prompt formatting work correctly before live deployment.

Yes, you must enable the webhook platform in your environment before subscribing. Once enabled, you can subscribe to routes for CI/CD pipeline notifications and store them persistently for hot-reloaded routing.