Connect GoHighLevel
This page takes you from nothing to a working connection: a GoHighLevel workflow that posts a lead to Booked55 every time an opportunity reaches a chosen pipeline stage, and a Booked55 connection that turns that post into a contact on your pipeline.
You need the owner or manager role in Booked55, and access to the GoHighLevel sub-account whose workflows you want to edit.
1. Create the connection in Booked55
- 1
Open Integrations
In the sidebar, expand Workspace, click Settings, then open Integrations. You need the owner or manager role.
- 2
Click "Connect" and choose GoHighLevel
Pick GoHighLevel as the provider. Give the connection a label that tells you which workflow it serves, for example "GHL – Appointment Booked", then click Create.
- 3
Copy the webhook URL
Booked55 shows the URL once, in the form https://api.booked55.com/inbound/inb_…, together with the GoHighLevel setup steps. Copy it now and keep it somewhere safe. Afterwards the Setup tab shows only a preview of the token, not the full URL.
2. Build the workflow in GoHighLevel
GoHighLevel sends the lead from a workflow. The trigger decides when a lead is sent; the Webhook action decides where.
- 1
Create a workflow
In GoHighLevel, go to Automation → Workflows and click Create Workflow.
- 2
Add the trigger "Pipeline Stage Changed"
Set the filter In Pipeline to the pipeline the lead lives in, and Pipeline Stage to the stage that means "hand this lead to sales". Assigned To, Tag, Lead Value, and Status filters are also available if you want to narrow it further.
- 3
Add the action "Webhook"
It is listed as Webhook (Outbound) in the action list. Set the method to POST and paste the URL you copied from Booked55. Any custom data key/values you add to the action are received too and kept on the contact as source data.
- 4
Save, then Publish
Save the workflow, then click Publish. A workflow that is saved but not published never fires.
3. Test the connection
- 1
Send a test event from Booked55
Open the connection, go to the Setup tab, and click Send test event. This runs a sample lead through the connection so you can confirm the settings before touching GoHighLevel. Test events are marked as tests in the event log.
- 2
Move a real opportunity in GoHighLevel
Drag an opportunity into the stage you chose as the trigger. GoHighLevel fires the workflow and posts the lead to Booked55.
- 3
Check the Events tab
Within seconds the event should show as processed, with a link to the contact it created or updated. If it shows failed or skipped, the event detail says why.
4. Check the Events tab
Every webhook the connection receives is listed on the Events tab, whether it succeeded or not. After your first real event, open it: you will see the raw payload GoHighLevel sent, the contact record Booked55 built from it, and links to the contact and company. If the status is anything other than processed, Event log & troubleshooting explains what it means and what to change.
What Booked55 imports
From each GoHighLevel opportunity and its contact, Booked55 takes:
| From GoHighLevel | In Booked55 |
|---|---|
| Name | The contact name (the full name, or first + last). |
| The contact email. | |
| Phone | The contact's primary phone number. |
| Tags | Contact tags, plus any tags the connection is set to add. |
| Contact source | A tag in the form Source: <contact source>. |
| Company name and website | A company, matched by name in the assignee's book or created if none matches, linked to the contact. |
| Address | City, state, country, and postal code. |
| Note in the webhook | A completed note task on the contact, if the payload carries one. |
| Full note history | A completed note task per note. Only when a Private Integration Token is set. |
| Opportunity details | Opportunity name, status, lead value, pipeline and stage names and ids, and location are kept on the contact as source data. |
If GoHighLevel sends several contacts in one request, which its workflow test panel can do when you select more than one contact, each becomes its own event and its own lead.
Every imported contact gets the source GoHighLevel. Notes become completed tasks of type “note”, which is what the Notes card on the contact page shows; a note that was already imported (same text) is not imported twice.
The connection's settings decide where the contact lands: which pipeline, which stage, who it is assigned to, and what happens if it already exists. See Connection settings & stage mapping.
Ready to get started?
Create your free Booked55 account and start managing your sales pipeline in minutes.