Why it matters
A webhook integration becomes difficult to operate when the customer cannot see what was sent. Delivery history turns failures into a debuggable workflow.
The console should separate the original event from its delivery attempts. Each attempt has an endpoint, time, response and retry status; sensitive payload fields may need redaction.
Decisions to make
- Choose how long delivery attempts and payloads remain available.
- Define who may inspect payloads or replay events.
- Decide whether replay preserves the original event ID and signature format.
- Set retry limits and backoff independently from manual replay.
- Plan secret rotation and endpoint changes without losing history.
Build checklist
- Record response code, duration and error for each attempt.
- Show the event ID, endpoint, payload version and signature timestamp.
- Provide a bounded manual retry with visible resulting attempt.
- Redact secrets and sensitive payload fields in support views.
- Test duplicate handling, timeouts and endpoint recovery.
Common mistakes
- Showing only a green or red status with no response details.
- Replaying an event with a new identity that breaks deduplication.
- Exposing complete payloads to every workspace member.
Tools & references
3 starting points to compare or study. Check fit, maintenance, terms and current capabilities before choosing one.
