Skip to main content

​
Configure a webhook

​
What this does

A webhook sends provider events to one fleet. agentsfleet verifies the request before creating an event. GitHub App events can use managed ingress. Other providers can use the fleet URL printed during installation.

​
Before you begin

Create a workspace secret that contains the provider’s signing secret. Add a webhook trigger to TRIGGER.md.

​
Steps

  1. Install or update the fleet.
  2. Copy the URL printed for the matching source.
  3. Register the URL and signing secret with the provider. For GitHub, open Repository settings → Webhooks → Add webhook. Choose the required event names.
  4. Send a provider test event. The provider owns delivery and retries. agentsfleet owns the URL until the fleet is deleted.

​
Verify it works

<FLEET_ID> comes from the install output.
A successful request returns HTTP 202. A filtered or inactive event returns HTTP 200 without opening a run.

​
Common problems

Providers can deliver the same event more than once. Use a stable provider event identifier and make fleet actions safe to repeat. Rate-limited requests include Retry-After. The provider should wait for that delay before retrying.

​
Remove or undo

Delete the webhook from the provider first. Then remove its trigger from TRIGGER.md and update the fleet. Deleting the fleet removes its webhook URL. Requests to the old URL then return UZ-WH-001.