FlowchartAPI workflowMedium
Webhook delivery with retry
Outbound webhook pipeline with signing, retry on failure, and dead-letter fallback.
What this diagram shows
Step 01
Signed delivery
Every event is signed before it leaves so the subscriber can verify authenticity.
Step 02
Retry budget
Transient failures get backed off and re-queued until the retry budget runs out.
Step 03
Dead-letter fallback
Permanently failing messages drop to a dead-letter queue for manual triage.
About flowchart diagrams
Flowcharts map out a process as boxes and arrows. They work well when you need to explain how a decision, workflow, or pipeline moves from one step to the next.
This template is written in Mermaid — plain text you can edit, version in git, and regenerate the image from any time.
View Mermaid sourcePlain-text diagram syntax — copy or edit directly.
diagram.mmd
1graph TD2 E[Event Occurs] --> Q[Enqueue Delivery]3 Q --> S[Sign Payload]4 S --> D[POST to Subscriber]5 D -->|2xx| OK[Mark Delivered]6 D -->|timeout or 5xx| R{Retry Budget Left?}7 R -->|yes| W[Backoff + Re-enqueue]8 W --> D9 R -->|no| DLQ[(Dead-letter queue)]Related
Related templates
More templates that cover similar workflows.
