# Monitor webhook delivery reliability

> Track failed, retried, and slow webhook deliveries by provider, event type, and customer before integrations silently break.

## Agent adaptation contract

- Canonical human page: https://agentry.sh/workflows/webhook-delivery-reliability
- Execution mode: on_demand
- Immutable automation template: none
- Applies to: b2b-saas, devtools-api, marketplace
- Required example events: webhook_delivery
- Required Agentry resources: none declared
- Do not use when:
  - Do not use until the example events are mapped to observed project signals, the current onboarding state is verified, and live event/property reads prove the required data is present.
- Ask before using:
  - Which observed events map to webhook_delivery? Is the current onboarding state verified, and do live event/property reads show non-synthetic traffic for them?
  - Which live properties provide webhook_delivery.provider, webhook_delivery.event_type, webhook_delivery.status, webhook_delivery.attempt, webhook_delivery.duration_ms, webhook_delivery.customer_id, and which stable user or account identifier joins the signals?

This is an adaptable workflow example, not an API recipe. Map event and property names to the project's saved signal map, require status: "verified" from GET /v1/projects/:project_id/onboarding, and confirm the required signals through live event/property metadata and rows. Fetch current OpenAPI or query-blueprint details before making calls. Do not infer unattended authority from this page.

## Why this matters

Webhook failures are support tickets with a delay. Your customer thinks your product stopped syncing, but the real signal is buried in retry logs. Agentry can rank unreliable integrations from the event stream.

## What you get

- Failure and retry rates by provider and event type
- Customers with repeated delivery problems
- Slow delivery outliers
- A short remediation plan: customer endpoint issue, provider outage, or your retry worker

## Walk through it

**You:**
> Which webhooks are failing this week?

**Agent:**
> I'll group delivery events by provider, event type, and customer.

```text
Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
  query: "SELECT properties.provider AS provider, properties.event_type AS event_type, properties.customer_id AS customer, count() AS deliveries, countIf(properties.status = 'failed') AS failed, countIf(toInt(properties.attempt) > 1) AS retried, quantile(0.95)(toFloat(properties.duration_ms)) AS p95_ms FROM events WHERE event = 'webhook_delivery' AND timestamp > now() - INTERVAL 7 DAY GROUP BY provider, event_type, customer ORDER BY failed DESC, retried DESC LIMIT 50"
```

## The output

The agent returns a list of customers and event types that need action. It should distinguish one-off retries from persistent failure and include whether failures started after a deploy.

## Setting it up

Emit `webhook_delivery` from the worker that sends outbound webhooks. Include both terminal failures and successful retries.

## Variations

- *"Alert if any enterprise customer has more than 10 failed deliveries in an hour."*
- *"Which event type is causing most retries?"*
- *"Compare webhook health before and after the new retry policy."*