Why does history not show the lead's name?
The history pages keep lead details private by design. Open Inbox to work with the lead itself.
Help Center
Check webhook deliveries, tests and operations
Read delivery history, send test events, replay a retained event and track each request with its operation ID.
The Lead webhooks pages show what was sent, what is waiting and what you asked for, without exposing lead details or secrets. Every test or replay request you make has an operation ID you can check later.
Use this guide when
A delivery failed, you want to confirm a test or replay request, or you need to explain what happened to a lead delivery.
Steps
- Open Account, then Lead webhooks, and choose Lead history or Test history.
- History covers the last 30 days and shows times in UTC. Payloads are retained for at most 7 days and can expire earlier, so older history may not be replayable. Use the state chips to filter deliveries. Tests have no retry state.
- Each entry shows its public event ID, its current state, the attempts so far and, once finished, the completed outcome with its HTTP status.
- To send a sample, open Test history and request one test. No real lead is created.
- To request the same retained event again, open the entry in Lead history and choose Request one replay. Up to three replays are allowed, one per hour, while the payload is retained.
- Save the operation ID shown with each request. It starts with op_. Check it at any time under Check operation.
History never shows lead details, saved URLs, signing secrets or receiver responses. It shows delivery states, attempts and outcomes.
Test limits and expiry
Tests let you check a receiver without a real lead. The limits are one unfinished test, one test per destination every five minutes and five tests per account in 24 hours. A test expires after 15 minutes.
What each operation result means
When a request is accepted, the page says so and points you to the matching history page for the delivery outcome.
When the original request target was deleted, such as the destination or the retained delivery, the page says the request cannot schedule more work.
When delivery is paused, the page says so and you can check the operation again later to reconcile any earlier acceptance.
On a conflict, the page says the operation ID belongs to a different submission. Do not reuse it for changed inputs.
A declined test was not scheduled, and the page shows the reason, such as a test limit being reached.
When the page reports the outcome as unknown, this does not confirm that nothing was scheduled. Check the same operation ID again.
Retrying safely
An accepted request records scheduling, not delivery. If a response is lost, check the original operation ID before doing anything else. Any explicit retry must reuse the same operation ID, so the same work is never scheduled twice. Opening a fresh history page creates new request IDs and does not reconcile an earlier request.
Plans and availability
Lead webhooks are included with Professional. Open Account, then Lead webhooks, and save your HTTPS destination to get started. Delivery begins only after you configure a destination and the service is available. Custom-plan access follows your agreement.
Good ways to use this
- Save operation IDs with your automation logs, so a lost response can always be reconciled.
- Check the state chips before assuming a delivery failed. A pending entry is still working.
- Use a test event whenever you onboard a new receiver or change its URL.
Common questions
The operation page says the request was accepted. What does that mean?
It means Zapped recorded the scheduling. The matching history page shows whether the delivery itself succeeded.
If something looks wrong
- If an entry keeps showing Automatic retry pending, your receiver has not answered successfully yet. Check the receiver and let the retries continue.
- If Check operation says the outcome is unknown, check the same operation ID again later before retrying anything.
- If a test is declined, read the reason. The limits allow one unfinished test, one per destination every five minutes and five per account in 24 hours.
Was this guide helpful?
Still have questions? Contact support and we'll help you out.