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

Skipped reasons

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, or apply) and an error code.
• Links — The contact and company the event created or updated.

Test events sent from the Setup tab are marked as tests, and are not used for the stage-name suggestions in the mapping editor.

Retry and Send test event

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.

Send test event, on the Setup tab, runs a sample lead through the connection without involving GoHighLevel. It is the quickest way to tell which side a problem is on: if a test event processes and real ones never arrive, the problem is in the GoHighLevel workflow, not in Booked55.

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 switch Active back on in the connection's Settings tab.

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 note tasks 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). Send a test event first: if it processes, 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 contact was already on a pipeline and the connection's Contact already on a pipeline setting is Leave where it is. Switch it to Move to the mapped stage if incoming events should move existing contacts.
• 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. Also check that Notes is set to Create note tasks.
• 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, and check the setting is not Always create.
• Lead assigned to the wrong person — The Assignee setting decides who the contact, its pipeline item, and its note tasks go to. It defaults to the acting user, which in turn defaults to whoever created the connection.

Every setting named above is described in Connection settings & stage mapping.