webhook-reliability

Ingest inbound webhooks and deliver outbound webhooks with at-least-once delivery.

Updated Mar 29, 2026

Search Tags:#reliability #deduplication #webhook #idempotency #retry #dead-letter #backoff

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill webhook-reliability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: webhook-reliability
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/webhook-reliability
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill webhook-reliability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In SaaS systems, webhook events can be lost, duplicated, or delayed. This Skill provides a robust pattern for reliable ingestion and delivery with deduplication, backoff, and dead-letter handling.

Core Features & Use Cases

Inbound: Accept immediately and process asynchronously to avoid provider timeouts, with deduplication by delivery ID and idempotent processing.
Outbound: Queue deliveries to customer endpoints with stable IDs for idempotency and DLQ support.
Observability: Track status, attempts, last_error, and trigger alerts on dead-lettering to ensure operator visibility.

Quick Start

Configure the webhook receiver to validate signatures, enqueue incoming payloads, and run a worker to process retries.

Frequently Asked Questions about webhook-reliability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I handle duplicate webhook deliveries and ensure idempotent processing?▼

To handle duplicate webhook deliveries, you enforce idempotent processing by deduplicating inbound payloads using a stable delivery ID. This ensures that processing the same webhook event multiple times yields the same result without duplicating side effects.

What is the best way to prevent webhook timeouts from external providers during ingestion?▼

The best way to prevent webhook timeouts is to accept inbound payloads immediately and process them asynchronously. By enqueueing the payload for a background worker, you avoid blocking the provider's HTTP request and hitting their timeout limits.

How do I configure retry policies with exponential backoff for outbound webhooks?▼

You configure outbound webhook retries using a worker-driven processing model with customizable retry policies. This approach applies exponential backoff to failed delivery attempts, ensuring at-least-once delivery to customer endpoints.

When should I move failed webhook deliveries to a dead-letter queue?▼

You should move failed webhook deliveries to a dead-letter queue (DLQ) after exhausting all configured retry attempts. Triggering alerts upon dead-lettering ensures operator visibility for endpoints that consistently fail to accept outbound events.

How does signature validation work for securing inbound webhook ingestion?▼

Signature validation secures inbound webhook ingestion by cryptographically verifying the payload against the provider's signature before enqueuing. This prevents unauthorized or tampered requests from entering your reliable delivery processing pipeline.

Do I need a dedicated worker model to guarantee reliable webhook delivery?▼

Yes, you need a dedicated worker-driven processing model to guarantee reliable webhook delivery. The worker manages the queue, executes retry policies with backoff, and handles dead-letter queueing, ensuring at-least-once delivery for both inbound and outbound events.