Import GoHighLevel leads into Booked55 automatically
GoHighLevel runs the front of the funnel: the landing pages, the SMS follow-ups, the appointment booking. Booked55 is where a rep works the relationship after that. This guide wires the two together with one workflow and one URL, so the hand-off stops being a copy-paste job.
What you get
- No copy-paste. The lead is created in Booked55 the moment it enters the trigger stage in GoHighLevel. Nobody exports a CSV or re-types a phone number.
- The lead arrives with context. Name, email, phone, company, address, the GoHighLevel tags, where the lead came from, and the note attached to the stage change. With a token, the whole note history follows.
- Duplicates get merged. A contact you already have is found by GoHighLevel id, email or phone and updated in place. What a rep typed is never overwritten.
- The sales process starts on the right stage. A stage mapping puts the lead on the Booked55 pipeline and stage you choose, so the follow-up automations for that stage start immediately.
Before you start
You need four things:
- Owner or manager role in Booked55. Integrations lives under Workspace → Settings and is available on every workspace.
- Admin access to the GoHighLevel sub-account. You will create a workflow there and a Private Integration Token, which lets Booked55 map your stages and bring the notes across.
- A decision on which GoHighLevel stage means “sales takes over”. That stage is the trigger. Everything before it stays in GoHighLevel; everything from it onward is worked in Booked55.
- Optionally, the Booked55 pipeline and stage the lead should land on. You can add this later. The connection works without it.
Step 1: Create the connection in Booked55
- Open Workspace → Settings → Integrations and click Connect.
- Choose GoHighLevel.
- Give the connection a name. It is only for you, so “GoHighLevel: main funnel” is fine.
- Fill in the Location ID. Open GoHighLevel in another tab, copy the whole address bar and paste it. Booked55 keeps the code after
/location/, and uses it to link you straight to the right pages in GoHighLevel. Click Create connection. - Answer the questions in the window that opens. They write a prompt for GoHighLevel's AI with your webhook URL already in it (Step 2).
The connection's name sits at the top of its page; click it to change it. Beside it is the Receiving leads switch. Below, a Navigation list on the left has three tabs.Setup starts with the webhook URL. It stays masked, and Copy puts it on your clipboard without showing it. Under it are the Location ID, the Private Integration Token and the GoHighLevel setup steps. Settings holds how leads are handled once they arrive. Events is the log of every webhook received.
Treat the URL as a password
The URL contains the connection's secret: anyone who has it can post leads into your workspace. If it ever leaks, open the connection, click Regenerate URL beside the URL, then paste the new URL into GoHighLevel. The old URL answers 404 from then on.
Step 2: Build the GoHighLevel workflow
One workflow sends Booked55 what you choose: a lead when an opportunity enters your hand-off stage, each call when it ends, its recording, what was said on it, and each text a contact sends. GoHighLevel's AI builds it from one prompt.
On the Setup tab, under Build the workflow, answer each question Yes or No. Click Copy prompt and open GoHighLevel. Click Build using AI there, paste the prompt into the chat and press Enter. When the AI finishes, it tells you what is left. If you send leads, choose your pipeline and stage. Check that Allow Re-entry is on in its Settings, so it runs for a contact's second call too, then publish it. Back in Booked55, answer Yes under the prompt. Booked55 looks for the workflow by its name, such as Booked55 Workflow 1, and shows Active once it is published.
The webhook carries a few Custom Data rows. They tell Booked55 who owns the contact in GoHighLevel, so each lead goes to the same rep, and whether the event is a lead, a call or a text. Calls and texts land only on contacts Booked55 already has, and each call becomes a task on the contact, with its recording.
Saved is not published
A workflow that is saved but not published never fires. This is the single most common reason “nothing arrives”. Check the publish toggle at the top of the workflow before you check anything else.
Step 3: Send a test lead
Move a test opportunity (or a throwaway one) into the hand-off stage in GoHighLevel and open the Events tab. Every webhook is listed with a status: received, processing, processed, failed or skipped. A processed event links to the contact it created or updated. A failed one shows the error and a Retry button. A skipped one shows why, for example duplicate, duplicate_contact or stage_not_mapped.
GoHighLevel's own test panel lets you pick more than one contact. Each one arrives as its own event and its own lead, so a batch of three test contacts shows up as three rows on the Events tab.
The Events tab is a recent log. Raw payloads are cleared after 7 days and events are deleted after 30.
Step 4: Add the Private Integration Token
The webhook carries the lead and at most one note. The token lets Booked55 read the rest from GoHighLevel: your pipelines and stages, so you can map them, your users, so you can see who gets each lead, and the contact's whole note history.
- In the Setup tab's Private Integration Token section, click Open Private Integrations in GoHighLevel. It opens that page for your sub-account.
- Click Create new Integration, name it “Booked55”, and select every scope. With all of them selected now, you never have to come back and add one. Booked55 uses the token to find and play call recordings, to check that your workflow is published, and to add contacts and send texts in GoHighLevel when you ask it to. Copy the token.
- Back in that section, paste the token and click Save token. Booked55 checks it with GoHighLevel straight away and tells you if it is wrong, or is missing a scope.
From then on, each imported lead brings its complete note history. Each GoHighLevel note becomes a note on the contact, in the Notes card on the contact page, keeping the date it was written in GoHighLevel — so the rep reads the story in the order it happened before the first call. Imported notes are marked Integration, so they read as coming from another system rather than typed by your team, and they sit on the card in date order with everything else. They are also not logged as activities, so nobody's activity count is inflated by somebody else's CRM. A note Booked55 has already imported is never imported twice, however many times GoHighLevel re-sends it.
Booked55 stores the token encrypted and only ever uses it to read. If GoHighLevel later rejects it (deleted, or a scope removed), the token section on the Setup tab says so. Leads keep importing; they just arrive without the history until you paste a working token.
Step 5: Map stages
A processed webhook creates or updates a contact. To also put that contact on a Booked55 pipeline, open the Settings tab. Where leads go has two sides, and saving one turns the other off. Default pipeline sends every lead to one pipeline and stage. Stage mapping sends each lead by its GoHighLevel stage, and its card follows the opportunity when it moves.
Stage mapping needs a second workflow. The one you built in Step 2 sends a lead only at the hand-off stage. The second, Send stage changes to Booked55, fires on every move in your pipeline, with no stage filter, and tells Booked55 to move the card. Booked55 gives you its prompt with a Copy button; once it is published in GoHighLevel, confirm it, and the stages open. Each GoHighLevel pipeline has its own tab, read with the token, so nobody types a stage name. Beside each stage pick the Booked55 stage it lands on, or leave it Not mapped, then save that tab.
| GoHighLevel pipeline | GoHighLevel stage | Booked55 pipeline | Booked55 stage |
|---|---|---|---|
| Sales | Appointment Booked | Sales Process | Appointment Set |
With that row, an opportunity moved into Appointment Booked in GoHighLevel's Sales pipeline becomes a contact on Appointment Set in Booked55's Sales Process pipeline.
Map the hand-off stage too: a lead at a stage left Not mapped comes in without a pipeline item. A move the second workflow reports for a contact Booked55 does not have is skipped as not_in_booked55; only the first workflow creates contacts.
If you only came for the setup, you can stop reading here. The connection is live. The rest of this page is for the day an event shows up as failed or a lead lands somewhere you did not expect, and you want to know what Booked55 was thinking.
What happens on every lead
Every webhook goes through the same three steps:
- Stored first. The webhook is written to the Events tab as received before anything else happens, so a lead is never lost to a downstream error. Payloads over 256 KB are rejected.
- Matched. Booked55 looks for an existing contact by the GoHighLevel contact id, then by email, then by phone.
- Created or updated. No match means a new contact. A match means the existing contact is updated.
An update fills fields that are empty, adds tags and phone numbers that are not there yet, appends notes it has not seen before, and moves the contact to the mapped stage, even when it is already on a Booked55 pipeline. It never overwrites something a rep typed, and it never changes the email or the owner. A team that would rather leave existing contacts alone, or always make a new one, can ask the Booked55 assistant to change that for the connection.
The company is matched by name or created, with its website when GoHighLevel had one. The opportunity itself (name, status, lead value, pipeline and stage, location) is kept with the contact as source data, so nothing GoHighLevel sent is thrown away. Every contact, company, pipeline item and note goes to the rep the Users section shows for that GoHighLevel user, or else to the person who set up the connection, with the contact source set to GoHighLevel.
Working the lead in Booked55
From here the lead is an ordinary contact on a stage. It carries a Source: <GoHighLevel source> tag (Source: Facebook Ads, Source: Website Form, whatever GoHighLevel recorded), the GoHighLevel tags, and any Tags you set on the connection. Because it landed on a stage, the rep gets that pipeline's activity automations from that stage: the first call task, the follow-up sequence, whatever you have configured. Deals, tasks and coaching work exactly as for any other contact, and the lead counts toward the funnel on the Sales Process page.
One thing this does not do: nothing flows back. A stage change or a note written in Booked55 is not sent to GoHighLevel. We went one direction on purpose, because a rep's working notes and a marketing system's contact record are different things. They sit in one list on the contact now, but each note still says where it came from, and a rep's own notes are the ones the card shows first. An official Booked55 app for GoHighLevel is planned (one-click install, no URL to copy), and whether it syncs both ways is the question we are still arguing about. The webhook connection you set up today keeps working either way.
Troubleshooting
Nothing arrives
The Events tab is the first place to look. If it is empty, the webhook never reached Booked55: the workflow is saved but not published, the filters do not match the stage you moved the opportunity to, the URL was pasted wrong (an unknown URL answers 404, which shows in the workflow’s execution log in GoHighLevel), Allow Re-entry is off in the workflow’s Settings and that contact already went through it once, or the connection is paused. A connection also pauses itself after 25 failures in a row; the Events tab shows why, and the Receiving leads switch at the top of the connection turns it back on.
Contact created, but no pipeline item
Where leads go is set to Stage mapping and the GoHighLevel stage is Not mapped, or nothing is set at all. Pick a Booked55 stage beside it on that pipeline's tab and save, or switch to Default pipeline, and the next lead lands where you want it.
Contact landed on the wrong stage
Open Stage mapping on the Settings tab. The Booked55 stage beside each GoHighLevel stage is where its leads go. If you renamed a stage in GoHighLevel after mapping it, pick a Booked55 stage for the new name. If the card stopped following later moves, check the second workflow, Send stage changes to Booked55, is published, and look for stage_not_mapped on the Events tab.
No notes came across
There is no Private Integration Token on the connection, or GoHighLevel stopped accepting it. The Private Integration Token section on the Setup tab says which. Click Replace token there, paste a new token and click Save token.
Duplicates
The email or phone differs between the two systems (a typo, a second address, a formatted number), so the match failed and Booked55 created a new contact. Once a contact has been imported it is matched by GoHighLevel id from then on, so a fix in either system holds. The reverse also happens: two GoHighLevel contacts that share a phone number, such as an office line, are one contact to Booked55.
Wrong owner
Open Users on the Settings tab. It lists each GoHighLevel user and the Booked55 person their leads go to: the one with the same email, or else the same name. To change it, give them the same email in both. Booked55 never reassigns an existing contact, so a change affects new leads only.
Event marked skipped: duplicate
An identical webhook within 10 minutes of the previous one is skipped on purpose, so a workflow that fires twice, or a retry from GoHighLevel, does not create two of everything.
Full reference
Every setting, status and field, on the docs site
This guide covers the path most teams take. The docs list every field on the connection, every event status, and exactly what is imported.
