Webhook event schema and debug template

How to test this template

Set up Webhook debugging template and check the results

Use the prompt to add events, then check the stored fields and query results. Review the event definitions before relying on the numbers.

1
Choose when to log
Instrument the point where webhook_received becomes final.
2
Create the contract
Start with webhook_received, webhook_processed, webhook_failed and keep every field typed, bounded, and privacy-reviewed.
3
Run a fixture
Exercise known success, failure, retry, and empty-result cases before relying on aggregate results.
4
Answer the question
Which provider events fail most often?

Template versus use case

Use this template to add events

Copy this template when the measurement goal is already clear. Use the matching use-case guide to review event boundaries, success definitions, and the decisions the resulting SQL should support.

Read Webhook debugging

Template

Paste this into your coding agent

Replace YOUR_API_KEY, run the flow locally, then verify the generated events and dashboards.

webhook-debugging

Webhook debugging template

text

Instrument webhook handling with Telemetry.

Use /skill.md and this Telemetry API key: YOUR_API_KEY

Log webhook_received, webhook_processed, webhook_failed, webhook_retried, and webhook_deduplicated with:
provider, event_type, route_template, status, status_code, latency_ms, attempt, idempotency_outcome, downstream_job_count, team_id, and error_type.

Create queries for volume by provider, failures by event_type, retry rate, duplicate rate, p95 processing time, and latest failed webhooks.

Do not log raw webhook bodies, signatures, secrets, payment details, or personal data.

Events to capture

webhook_receivedwebhook_processedwebhook_failedwebhook_retriedwebhook_deduplicated

Verification checklist

Check the events, queries, and dashboard

Events

Synthetic events reach the intended table with stable names and field types.

Queries

The first SQL queries return plausible rows with an explicit time window.

Views

A dashboard uses the real fields and includes enough context to explain a change.

Safety

You checked that events exclude prompts, bodies, credentials, signatures, and private content.

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Integration reliability11 fields