Webhook Integration taste — ChatGPT prompt
The Webhook Integration taste ChatGPT prompt sets rules for reliable webhook integrations. It covers event intake, processing, and delivery to customer endpoints.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Webhook Integration taste does
The prompt lays out how to receive and send webhooks with signature checks and replay protection. For incoming events, it calls for verifying an HMAC over the raw request body before parsing JSON, using constant-time signature comparison, and storing each event before a background worker processes it. Deduplication uses the event ID; a version or updated_at field helps handle out-of-order events.
For outgoing webhooks, the prompt specifies retries with exponential backoff and jitter, a delivery log, and manual replay. It also calls for blocking URLs that resolve to private, loopback, or link-local addresses. Endpoints outside local development must use HTTPS. The guidance also covers secret rotation, recovery from missed events, and failure alerts.
What it helps with
- verify webhook signatures before parsing JSON
- deduplicate repeated event deliveries
- handle events that arrive out of order
- retry failed outgoing deliveries with backoff
- block SSRF attempts through webhook URLs
Example prompts for the agent
- Design an incoming webhook handler with signature checks and replay protection.
- Add outgoing webhooks with retries and a delivery log.
- Review this webhook design for event ordering, secret rotation, and unsafe URLs.
How to install Webhook Integration taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Webhook Integration taste
How do I install Webhook Integration taste in Claude Code?
Add the prompt to .claude/commands/prompts.csv.md.
What does Webhook Integration taste do?
It sets guidance for receiving and sending webhooks, including signature verification, deduplication, retry behavior, and delivery logs.
How does the prompt secure outgoing webhooks?
It requires HTTPS outside local development and blocks URLs that resolve to private, loopback, or link-local addresses.
Source text
prompts.csv · CC0-1.0
# Webhook Integration taste of a reliability-focused integrations engineer - Verify every incoming webhook with an HMAC signature over the raw request body before parsing it as JSON. Confidence: 0.95 - Compare signatures with a constant-time function, never with a plain string equality check. Confidence: 0.95 - Reject deliveries whose signed timestamp is older than about five minutes to block replay attacks. Confidence: 0.90 - Respond with a 2xx status within a few seconds and do the real work in a background job. Confidence: 0.95 - Persist the raw event first, then process it, so nothing is lost if a worker crashes mid-way. Confidence: 0.90 - Deduplicate on the provider's event ID with a unique index, because every provider retries and delivers at least once. Confidence: 0.95 - Never assume events arrive in order, and compare a version or updated_at field before overwriting local state. Confidence: 0.85 - Treat the payload as a hint and refetch the current object from the provider's API for anything money-related. Confidence: 0.80 - Return 4xx only for permanently bad requests and 5xx for temporary failures so the sender's retries behave correctly. Confidence: 0.85 - Support at least two active signing secrets at once so secrets can be rotated without downtime. Confidence: 0.85 - When sending webhooks, retry with exponential backoff and jitter for up to a day or more, then disable the endpoint and notify its owner. Confidence: 0.90 - Send a thin, versioned payload with an event type, event ID, timestamp and resource ID instead of dumping whole database rows. Confidence: 0.80 - Name event types as resource.action in the past tense, like invoice.paid or user.deleted. Confidence: 0.80 - Give customers a delivery log with request, response, status and a manual replay button. Confidence: 0.85 - Block outgoing webhook URLs that resolve to private, loopback or link-local addresses to prevent SSRF. Confidence: 0.95 - Use separate, short timeouts for outgoing deliveries and never let one slow customer endpoint block a shared queue. Confidence: 0.90 - Require HTTPS for all webhook endpoints outside local development. Confidence: 0.90 - Offer a reconciliation API or periodic sync so consumers can recover from missed events. Confidence: 0.80 - Test handlers locally with the provider's CLI or a tunnel, and keep recorded sample payloads as test fixtures. Confidence: 0.80 - Alert on rising failure rates and growing backlogs per endpoint, not only on individual errors. Confidence: 0.80 - Never log full payloads that contain personal data, secrets or card details. Confidence: 0.90
© f · CC0-1.0 · f/prompts.chat