Test, Monitor, and Retry Deliveries
Use delivery history to confirm webhook health, inspect receiver responses, and recover from failed deliveries.
The Webhooks integration includes delivery history for tests and subscribed contact events. Use it to confirm events are reaching the receiver and to troubleshoot receiver errors.
Send a test delivery
Open Webhooks
Open Integrations, choose Webhooks, and stay on the Destinations tab.
Find the destination
Locate the destination you want to test.
Send test
Open the row action menu and choose Send test.
Review the delivery
Leadpush creates a webhook.test delivery and opens it in the delivery detail view.
Confirm the receiver
Check the receiving system logs to confirm the request was accepted and signature verification passed.
Delivery statuses
| Status | Meaning |
|---|---|
pending | The delivery was created and is waiting to be sent. |
processing | Leadpush is currently sending the delivery. |
retrying | The last attempt failed, and Leadpush will retry. |
succeeded | The receiver returned a successful HTTP response. |
failed | Delivery attempts are exhausted or the delivery cannot be sent. |
Delivery detail
Open a delivery to review:
- event type and event id
- destination name
- rendered method and URL
- response status
- response body excerpt
- error message
- attempt count
- next retry time
- individual attempt history
Leadpush stores response excerpts to help troubleshoot receiver failures without turning delivery history into a full payload archive.
Filter delivery history
Use filters to narrow delivery history by:
- destination
- event type
- delivery status
Common views include failed deliveries for a destination, all webhook.test deliveries, or all deliveries for a specific contact event type.
Retry failed deliveries
Retry is available for failed deliveries.
Fix the receiver
Resolve the receiver problem first, such as authentication, URL routing, validation, or timeout errors.
Open the failed delivery
Open the delivery detail from the Delivery History tab.
Retry delivery
Click Retry Delivery.
Watch the status
Refresh or reopen the delivery to confirm it moves to pending, then succeeded or another failure state.
Common failure causes
| Symptom | What to check |
|---|---|
401 or 403 response | Receiver auth header, token, or allowlist. |
404 response | URL template and receiver route. |
422 response | Receiver validation rules and body template shape. |
500 response | Receiver server logs. |
| Timeout | Destination timeout and receiver processing time. |
| Signature rejected | Raw body verification and current signing secret. |
Production monitoring tips
- Send a test delivery after creating or editing a destination.
- Send another test after rotating a signing secret.
- Keep receiver logs searchable by
X-Leadpush-Delivery. - Alert on repeated failed deliveries for critical receivers.
- Disable a destination before planned receiver maintenance if failures are expected.