Implement webhook systems for event-driven integration with retry logic, signature verification, and delivery guarantees. Use when creating event notification systems, integrating with external services, or building event-driven architectures.
3f5182cBuild reliable webhook systems with event delivery, signature verification, retry logic, and dead-letter handling for asynchronous integrations.
Minimal working example:
{
"id": "evt_1234567890",
"timestamp": "2025-01-15T10:30:00Z",
"event": "order.created",
"version": "1.0",
"data": {
"orderId": "ORD-123456",
"customerId": "CUST-789",
"amount": 99.99,
"currency": "USD",
"items": [
{
"productId": "PROD-001",
"quantity": 2,
"price": 49.99
}
],
"status": "pending"
},
"attempt": 1,
"retryable": true
}
Detailed implementations in the references/ directory:
| Guide | Contents | |---|---| | Webhook Event Schema | Webhook Event Schema | | Node.js Webhook Service | Node.js Webhook Service | | Python Webhook Handler | Python Webhook Handler | | Best Practices | Best Practices, Webhook Events |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/webhook-development · pinned to the source commit
git clone https://github.com/aj-geddes/useful-ai-prompts.git
cd useful-ai-prompts
git checkout 3f5182cfd739fc113f4af5244a1cf342ad7f7911
mkdir -p ".claude/skills/webhook-development"
cp -r "skills/webhook-development" ".claude/skills/webhook-development"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 3f5182cfd739. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.