Webhook Event Schema and Debug Template

Template evidence path

Webhook Debugging Template: implementation to decision

Treat the prompt as an implementation brief. The useful artifact is not copied code alone, but a reviewed event contract that produces a trustworthy answer.

1
Select the boundary
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

This page is the implementation brief

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

What a complete instrumentation pass leaves behind

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

Prompts, bodies, credentials, signatures, and private content were checked for redaction.

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

Integration reliability11 fields