Debug webhooks
Diagnose why webhook notifications are not arriving by inspecting recent delivery attempts.
User intents
"My webhook isn't firing — what's wrong?" "Show me the last webhook deliveries and their status."
Required information
- Nothing required to list; optionally an event type or date range to narrow the search.
Tool sequence
List recent deliveries
list_webhook_deliveries — review each attempt's HTTP response status and timestamp.
Correlate with the assignment
For a delivery tied to a publish event, get_assignment confirms the underlying state that triggered (or should have triggered) the webhook.
Identify the failure pattern
Look for non-2xx response codes, timeouts, or missing deliveries to pinpoint whether the issue is the receiver endpoint or the event itself.
A non-2xx response recorded against a delivery means your endpoint rejected or failed to accept it. Fix the receiver before expecting retries to succeed.
REST alternative
The webhook delivery log endpoint backs this tool — see the Webhooks reference.
Recovery paths
- Deliveries show non-2xx — fix the receiving endpoint (auth, TLS, response code) and verify it returns
2xx. - No deliveries at all — confirm a webhook is configured and that the triggering event (e.g. a publish) actually occurred via
list_assignments. - Signature rejected on your side — verify your signature-validation logic against the documented scheme.
Example prompt → result
"Show me the last webhook deliveries and tell me why my endpoint isn't receiving them."
Result: the agent lists recent attempts, surfaces the failing response codes, and points to the receiver as the cause.
Common mistakes
- Blaming Pharlo for missing notifications when the receiver returned a non-2xx status.
- Expecting webhooks for events that never occurred (no matching assignment).