Event log & troubleshooting
The Events tab of a connection lists every webhook it has received. Booked55 stores each one before it applies anything, so the log is complete: a lead that failed to import is there alongside the ones that succeeded, with the reason.
Statuses
| Status | Meaning |
|---|---|
received | Stored, not yet processed. Events normally leave this status within seconds. |
processing | Being applied right now. |
processed | Applied. The event links to the contact and company it created or updated. |
failed | A processing stage failed. The event shows which stage and an error code, and can be retried. |
skipped | Stored but deliberately not applied. The event shows the reason, and can be retried. |
Skipped reasons
| Reason | Meaning |
|---|---|
duplicate | The same payload arrived within 10 minutes of the previous one. GoHighLevel sometimes re-fires a workflow; Booked55 stores the repeat and skips it so the lead is not applied twice. |
duplicate_contact | A matching contact already exists and the connection's Duplicates setting is Skip. |
team_address | The lead's email address belongs to someone on your team, or is on your company's own email domain. For privacy, people on your own team are never contacts, so the event is left alone and does not count against the connection. |
own_contact | Booked55 added this contact to GoHighLevel itself, when someone opened them there to call or text or sent a mass text. GoHighLevel then reported them as a new contact. They were in Booked55 first, so nothing is changed. |
org_suspended | Your organization was suspended when the event arrived. The event is kept and can be retried after reinstatement. |
feature_disabled | Integrations were switched off for your account by Booked55. This is not the default; contact us, then retry. |
org_inactive | Your organization had no active subscription when the event arrived. The event is kept and can be retried once the subscription is active again. See When there is no active subscription. |
not_in_booked55 | A stage move, a call, a text or a payment came for a contact that is not in Booked55. None of these creates a contact: the lead workflow does that when the lead reaches your hand-off stage. |
stage_not_mapped | The stage workflow reported a move to a GoHighLevel stage that has no mapping. The card stays where it is. Map that stage on the Settings tab if moves to it should follow. |
payment_not_paid | The payment's status is not a word for money that came in. A refund or a partial payment is skipped this way, and nothing changes in Booked55. See Payments. |
duplicate_payment | Booked55 already recorded a payment with this id, so it is not counted twice. |
What an event shows
Open any event to see:
- Raw payload — Exactly what GoHighLevel sent, including any custom data from the Webhook action.
- Built record — The contact record Booked55 assembled from the payload: name, email, phone, tags, company, address, notes, and the pipeline and stage it resolved to.
- Stage and error code — For a failed event, which processing stage failed (
normalize,enrich,map,validate, orapply) and an error code. - Links — The contact and company the event created or updated. A payment links to its contact and its invoice.
A note in the payload becomes a note on the contact, in its Notes card, keeping the date it carried in GoHighLevel and marked Integration so it is clear nobody on your team typed it. Imported notes are not logged as tasks — bringing another CRM's note history across does not inflate anyone's task counts.
A test event from before November 2026 is marked as a test and does not count towards the failures that disable a connection.
Retry
Retry re-runs a failed or skipped event from its stored payload. Fix the cause first (add the missing stage mapping, switch the connection back on, replace the token), then retry. The stored payload is cleared 7 days after receipt, so retry within that window.
Automatic disabling
After 25 consecutive failed events, Booked55 disables the connection. From then on it answers 404 to GoHighLevel and stores nothing, until you fix the cause and turn Receiving leads back on at the top of the connection's page.
Retention and limits
- Raw payloads and the built record are cleared 7 days after receipt.
- The event row itself is deleted after 30 days.
- Payloads over 256 KB are rejected.
- A request carrying a list of contacts stores one event per contact, up to 50 per request.
The contacts, companies, pipeline items, and notes an event created are not affected by retention; only the event log entry is.
Troubleshooting
- Nothing arrives — In order of likelihood: the GoHighLevel workflow is saved but not published; the trigger filters (In Pipeline, Pipeline Stage) do not match the opportunity you moved; the URL in the Webhook action is wrong or belongs to a regenerated URL; the connection is disabled (Active is off, or it was disabled automatically). To test, move an opportunity into the trigger stage in GoHighLevel: if nothing shows in the event log while the connection is Active, the problem is on the GoHighLevel side.
- Contact created but no pipeline item — No stage mapping row matched the pipeline and stage names GoHighLevel sent, and no default pipeline and stage is set. Open the event, compare the names in the raw payload with your rows, and fix the row or set a default so the next lead maps. Put this contact on the pipeline by hand from its contact page.
- Contact not on the expected stage — The lead workflow sends a lead once, when it reaches your hand-off stage. Later moves reach Booked55 only through the stage workflow that Stage mapping asks for. Check that it is published and has no stage filter, and look on the Events tab for a
stage_not_mappedevent: that stage needs a mapping. - Failed with
inbound_value_required_for_client_stage— The event would have put the contact into a client stage, which creates a deal, and the GoHighLevel opportunity had no Lead Value above 0. Nothing from the event was imported. Give the opportunity a Lead Value in GoHighLevel and move it into the stage again so the workflow sends a new event; Retry replays the same payload, so it fails again unless the contact's card in Booked55 now has a value of its own. See Client stages need a value. - Failed with
inbound_payment_invalid— The payment came with no id or no amount Booked55 can read. GoHighLevel's AI leaves out a row when it finds no field for it, so check that the workflow's Webhook action hascustom_payment_idandcustom_amount. Retry replays the same payload, so it fails again. Mark this invoice paid by hand: Marking an invoice paid. - Failed with
inbound_payment_failed— Booked55 could not record the payment. Click Retry. The same payment is never counted twice. - A payment made a new deal — No unpaid invoice on the contact had that exact amount, so Booked55 made a one-time deal marked Check the schedule. If the money belongs to another invoice, an owner or a manager clicks Undo paid on the new invoice, deletes the new deal, and marks the right invoice paid by hand.
- No notes — No Private Integration Token is set, or the connection shows Credentials invalid. Without a valid token only the note carried in the webhook itself is imported. Save a new token on the connection's Setup tab (Replace token, if one is already saved).
- Duplicate contacts — Booked55 matches on the GoHighLevel contact id, then email, then phone. If the email or phone differs between the two systems, or is missing in one of them, a second contact is created. Align the email and phone in both systems.
- Lead assigned to the wrong person — A lead goes to the Booked55 person with the same email as its GoHighLevel owner, or else the same name, and to the person who set up the connection when nobody matches. With the token saved, the Users section on the Settings tab shows who each GoHighLevel user's leads go to. Give the two the same email to fix one.
Every setting named above is described in Connection settings & stage mapping.
Ready to get started?
Create your free Booked55 account and start managing your sales pipeline in minutes.