webhook-subscriptions

You can trigger automated agent runs from external events by creating webhook subscriptions that allow services like GitHub or Stripe to post event payloads to a configured gateway URL. The subscription matches incoming events and executes the linked agent prompt.

Yes, webhook subscriptions support prompt templates with placeholders for accessing nested payload fields. This allows you to dynamically insert values like issue numbers or user logins from the incoming event data directly into your agent instructions.

Webhook event notifications can be delivered to various targets including Telegram, Discord, and GitHub comments. You configure these delivery channels when creating the subscription to route automated agent outputs to your preferred platform.

Yes, managing webhook subscriptions requires a configured Quill Agent gateway to receive incoming event payloads. You must set up this gateway and configure the specific webhook platforms for services like CI/CD pipelines or IoT sensors before subscribing.

You can list, remove, and test existing webhook subscriptions to manage event-driven automation. Testing subscriptions verifies that incoming events correctly trigger the configured agent runs and deliver notifications to the designated targets.