Telemetry
For teams that depend on Stripe, GitHub, customer, or provider webhooks

Webhook Debugging

Track webhook delivery, processing, retries, deduplication, downstream jobs, and failures without storing raw payloads.

Get an API keyCopy the prompt
Why this works
  • See failures by provider, event type, endpoint, and downstream job.
  • Measure retry and duplicate rates from real webhook processing events.
  • Create an audit trail that helps debug revenue and integration issues.

Agent prompt

Paste this into your coding agent

Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.

agent prompt

Webhook Debugging setup prompt

text
Instrument webhook debugging with Telemetry.

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

Please log webhook_received, webhook_processed, webhook_failed, webhook_retried, and webhook_deduplicated. Include 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.

Setup steps

  1. 1Log webhook_received, webhook_processed, webhook_failed, and webhook_retried.
  2. 2Capture provider, event type, status, latency, attempt, and idempotency outcome.
  3. 3Connect downstream jobs or billing syncs triggered by each webhook.
  4. 4Create alerts for repeated failures, retry spikes, and processing latency.

Events to capture

webhook_receivedwebhook_processedwebhook_failedwebhook_retriedwebhook_deduplicatedbilling_sync_failed

Questions unlocked

  • Which webhook event types fail most often?
  • Are retries fixing failures or creating duplicates?
  • Which downstream systems are affected by provider delays?

Next step

Create the API key your agent will use

The free plan is enough to run the prompt, send test events, and review the first dashboard.

Prompt packStart free

Related pages

Claude Code Observability

Give Claude Code a prompt that makes telemetry part of the implementation pass instead of a separate cleanup project.

Open page

Cursor Telemetry Setup

A copyable setup prompt for adding event tables, funnel tracking, and dashboards from inside Cursor.

Open page

Codex Instrumentation Prompt

A focused prompt that asks Codex to instrument the rest of the product, verify events, and summarize coverage gaps.

Open page