A lead didn’t reach my CRM

There are three different failures behind “the lead never arrived”, and the delivery log tells you which one you have in about ten seconds.

1. Was a delivery even attempted?

Open the Lead qualifier page and look at “Recent deliveries”. No entry for that lead means we never tried. The usual cause is the “Which leads to send” setting: on “Qualified leads only”, a lead that is still being asked questions or was disqualified sends nothing at all — not even their messages or delivery receipts. Switch to “All leads, with their qualification status” if you want them. The other cause is an empty webhook URL.

2. Was it attempted and refused?

A failed entry shows the HTTP code your endpoint returned and the error text. Read them literally:

• 401 or 403 — your endpoint rejected our request. Usually signature verification against a re-serialised body instead of the raw bytes, or the wrong secret.
• 400 or 422 — your endpoint parsed the payload and did not like it. We do not retry these, because the next identical attempt fails the same way.
• 5xx or a timeout — your endpoint was down or slow. We retried four times over about six minutes; after that it stays failed in the log.
• “Blocked: the URL points to a private or reserved address” — the URL resolves inside a private network, which we refuse to call.

Once your endpoint is fixed, use “Redeliver” on the Integrations page. It reuses the original delivery id, so a receiver that de-duplicates on that id will not create a duplicate lead.

3. Did it arrive and get dropped on your side?

A delivered entry means your endpoint returned a 2xx. At that point the lead is in your systems and the question is what your handler did with it. Check the delivery id in the log against your own logs — that is the id we sent in the X-WABridge-Delivery header.