Connect GoHighLevel
This page takes you from nothing to a working connection. One GoHighLevel workflow posts a lead to Booked55 every time an opportunity reaches a chosen pipeline stage, and posts each call and text as it happens. It can also post each new contact as soon as it is made, and each payment. A Booked55 connection turns each lead into a contact on your pipeline, and each call into a task on that contact. A payment marks the invoice it matches as paid.
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, open the Workspace Settings dropdown, and click Integrations. You need the owner or manager role.
- 2
Click "Connect" and choose GoHighLevel
Connect opens the Add an integration page, which lists every system Booked55 can receive contacts from. Click the GoHighLevel card. Give the connection a label that tells you which workflow it serves, for example "GHL – Appointment Booked". For the Location ID, open GoHighLevel in another tab, copy the whole address bar and paste it: Booked55 keeps the code after /location/. Then click "Create connection".
- 3
Answer the questions
Booked55 then opens a window that asks what you want to send, one Yes or No at a time, and writes the prompt for GoHighLevel's AI, with your webhook URL already in it (see below). The URL, in the form https://api.booked55.com/inbound/inb_…, stays masked at the top of the connection's Setup tab: Copy puts it on your clipboard without showing it, any time.
2. Build the workflow in GoHighLevel
One GoHighLevel workflow sends what you choose: leads, new contacts, calls, recordings, what was said on each call, texts and payments. Any one of its triggers starts it. The triggers decide when something is sent; its one Webhook action decides where.
Let GoHighLevel's AI build it
When you create the connection, Booked55 asks a few Yes or No questions: leads, new contacts, calls, recordings, what was said on each call, texts and payments. The connection's Setup tab asks the same ones, under Build the workflow. Anything you say no to stays out of the workflow. Then:
- Click Copy prompt and open GoHighLevel. It copies a prompt with your webhook URL in it, and opens your Workflows page.
- Click Build using AI in GoHighLevel. Click in the chat box, paste the prompt and press Enter.
- Wait for the AI to finish. It tells you what is left. If you send leads, choose your pipeline and stage on the Pipeline Stage Changed trigger. If your leads come from somewhere else, such as a form or a calendar booking, say so in the chat and the AI changes that trigger.
- Click Publish. The AI never publishes a workflow for you, and a workflow does nothing until it is published. The prompt turns on Allow Re-entry in its Settings: without it, GoHighLevel runs the workflow only the first time for each contact, so a contact's second call never reaches Booked55. To change anything, keep talking to the AI in GoHighLevel.
You answer once. After that the Setup tab shows what your workflow sends, with a tick beside each thing, and the prompt. Each workflow has a number in its name, starting with Booked55 Workflow 1, so keep that name in GoHighLevel.
When you answer Yes to Did you create the workflow and publish it?, Booked55 looks for that name in GoHighLevel with your Private Integration Token. If it is published, the prompt goes and the tab says Active. If it is missing, still a draft, or the workflow before it is still published, Booked55 says what to fix. With no token, or if GoHighLevel cannot say, it takes your word.
A new webhook URL brings the prompt back with the next number, because the old workflow still sends to the old address. To send more later, click Create a new workflow, answer again, delete your old workflow in GoHighLevel, and build the new one. If both are on, everything arrives twice.
A workflow you already built keeps the answers you gave. It does not pick up a question Booked55 added later, so new contacts and payments show without a tick on the Setup tab. To add them, click Create a new workflow.
With a yes to everything, the prompt reads like this, with your own URL in place of the square brackets:
Create a workflow named "Booked55 Workflow 1".
Add these triggers. Any one of them starts the workflow:
- Pipeline Stage Changed. Leave its pipeline and stage empty. I will choose them after you finish.
- Contact Created.
- Call Details, with one filter: Call Status is completed, no-answer, busy, voicemail or canceled. Do not add a Call Direction filter, so incoming and outgoing calls both run it.
- Customer Replied, with one filter: Reply channel is SMS.
- Payment Received.
Action: one Webhook (Outbound), run by every trigger.
- Method: POST
- URL: [YOUR BOOKED55 WEBHOOK URL]
- Keep the standard data in the payload.
- Under Custom Data, add these items. Write each Key exactly as here. Where the Value is in quotes, type what is inside the quotes, without the quotes; otherwise use the merge field that holds what it describes:
Key booked55_event, Value "auto"
Key owner_email, Value "{{user.email}}"
Key owner_first_name, Value "{{user.first_name}}"
Key owner_last_name, Value "{{user.last_name}}"
Key call_direction, Value the call's direction (inbound or outbound)
Key call_status, Value the call's status
Key call_duration, Value the call's duration
Key call_from, Value the phone number the call came from
Key call_to, Value the phone number the call went to
Key call_started_at, Value the date and time the call started
Key text_body, Value "{{message.body}}"
Key custom_payment_id, Value the payment's id
Key custom_amount, Value the amount paid
Key custom_currency, Value the payment's currency code
Key custom_paid_at, Value the date the payment was made
Key custom_status, Value the payment's status, or paid if no merge field holds it
- If no merge field holds what a Value describes, leave that item out. Never type the description into a Value, and do not ask me to fill it in.
Settings: turn on "Allow Re-entry", so the workflow runs every time and not only the first time for each contact.
Do not add any other actions.
When you finish, do not ask me anything. Tell me in plain words what is left for me to do:
- Choose my pipeline and stage on the Pipeline Stage Changed trigger.
- Click Publish. The workflow does nothing until it is published.The Custom Data rows
Each run sends every row, but only the rows its trigger knows come filled. That is how Booked55 tells a lead, a call, a text and a payment apart.
| Key | What it carries |
|---|---|
booked55_event | auto: Booked55 works out from the other rows what happened. If you said no to leads it is auto_activity, and a run that is no call, text or payment is skipped. |
owner_email, owner_first_name, owner_last_name | The GoHighLevel user who owns the contact: {{user.email}}, {{user.first_name}} and {{user.last_name}}. A new contact goes to the same person in Booked55. |
call_direction to call_started_at | The call: its direction, status, length, phone numbers and start time. GoHighLevel's AI has no field for a call's id or recording, so Booked55 finds those itself (see Calls, texts and recordings). |
text_body | The text a contact sent. |
custom_payment_id to custom_status | The payment: its id, amount, currency code, date and status. Only the Payment Received trigger fills them. See Payments. |
keep_recording, keep_transcript | no, only if you said no to recordings or to what was said on each call. Booked55 then keeps no recording of that call, or makes no transcript from one. |
Booked55 reads them in this order. A filled payment id or amount makes it a payment. An event with a pipeline is a lead. A call status or a call length makes it a call, and a filled text_body a text. Anything else is a lead, which is how a run from Contact Created counts.
Without the owner rows contacts still arrive, but they may all go to the person who set up the connection, because GoHighLevel does not always send the owner by itself. See Who gets each contact.
3. Test the connection
- 1
Move a test opportunity in GoHighLevel
Drag an opportunity into the stage you chose as the trigger. GoHighLevel fires the workflow and posts the lead to Booked55.
- 2
Make a test call
From GoHighLevel, call a contact Booked55 already has. When the call ends, it shows on a task with that contact, under their Calls.
- 3
Check the Events tab
Within seconds each 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.
5. Add the Private Integration Token
Optional, and worth it. The Private Integration Token section of the connection's Setup tab links straight to Private Integrations in your sub-account, and takes a Private Integration Token. When you create it in GoHighLevel, select every scope, so you never have to come back and add one. Booked55 checks the token with GoHighLevel when you save it. With it, Booked55 finds and plays call recordings (see Calls, texts and recordings), checks that your workflow is published, opens a contact in GoHighLevel when you click their phone number, and sends mass texts from your GoHighLevel number. The Settings tab maps your GoHighLevel stages to Booked55 stages, lists who each GoHighLevel user's leads go to, and every contact comes with its full note history. See Private Integration Token.
This workflow sends a lead when it reaches your hand-off stage. To move its card in Booked55 each time the opportunity moves after that, use Stage mapping, which adds a second workflow.
6. Calls, texts and recordings
The same workflow sends your GoHighLevel calls and texts. Each call becomes a task on the contact, with its recording and what was said on it, and shows under the contact's Calls. Each text a contact sends shows under their Texts. Two of its triggers do this:
| GoHighLevel trigger | In Booked55 |
|---|---|
| Call Details, with Call Status completed, no-answer, busy, voicemail or canceled | The call goes on a task with the contact. It completes that person's open call task with the contact due that day, or else makes a completed “Called” or “Call from” task. A call in that nobody answered leaves an open “Call back” task. The recording plays on the task and under Calls. |
| Customer Replied, with Reply channel SMS | The text under the contact's Texts, counted on one task with the contact for that day. |
The task goes to whoever made or took the call, even when someone else owns the contact: the Booked55 user with the same email as the GoHighLevel user on the call, or else the same name. A text that comes in goes to the person who last texted that contact. If GoHighLevel names nobody, or that person has no Booked55 login, it goes to the contact's owner. Calls and texts only land on contacts already in Booked55: one from a number Booked55 does not know shows as skipped in the Events tab, and no contact is made for it.
GoHighLevel has no trigger for a text your team sends, so Booked55 reads those itself every 10 minutes. This needs a Yes to texts and the Private Integration Token. Each text shows under the contact's Texts and goes to the person who sent it, even when someone else owns the contact. It completes their open text task for that day, or counts on the day's task. Booked55 leaves out texts that a workflow, a campaign or a bulk action sent, texts that failed, and texts to anyone not in Booked55. These texts do not show in the Events tab, because GoHighLevel did not send them.
Booked55 finds each recording itself. When a call is reported, it uses the Private Integration Token to look through the contact's GoHighLevel conversation for that call. Without the token, or with one that has only some scopes, the call still lands, with no recording. GoHighLevel records only some calls, so a call with nothing to play shows no player.
The recording stays in GoHighLevel. Booked55 keeps its link and plays it from there, only for people who may see the contact. If you said yes to what was said on each call, Booked55 writes the recording out with each voice named, and adds short notes on the task, so you do not need GoHighLevel's own transcription.
Whether GoHighLevel records a call, and what the people on it are told, is set in GoHighLevel: the contact's Do not record flag covers Booked55's own recording only. A text that says STOP marks the contact Do not text.
7. New contacts
If you said yes to Send each new contact to Booked55 as soon as it is made?, the workflow also runs on GoHighLevel's Contact Created trigger. The contact shows up in Booked55 right away, so you do not wait for a lead to reach your stage. Booked55 asks this only after a yes to leads.
A contact from this trigger has no GoHighLevel stage yet. With a Default pipeline, it lands on that pipeline. With Stage mapping, it has no pipeline card until its opportunity reaches your hand-off stage. When that happens Booked55 finds the contact it already has and updates it. See When a contact already exists.
Every contact from GoHighLevel keeps the date it was created there. Booked55 writes that date once and never changes it. The KPI tiles that start from the lead, such as Speed to lead and Lead to close, count from it. Without it they count from the day the contact reached Booked55.
Every new contact also gets the automatic enrichment lookup, which uses credits when it finds the person. This trigger can bring in far more contacts than a stage does. An owner or manager can turn the lookup off on the Data & privacy tab.
8. Payments
If you said yes to Mark invoices paid when money comes in through GoHighLevel?, the workflow also runs on GoHighLevel's Payment Received trigger, and each payment marks the matching invoice paid. Say yes only if money actually goes through GoHighLevel. Payments need no Private Integration Token.
Booked55 records the money GoHighLevel reports. It never collects money itself. A payment counts the same as a person clicking Mark as paid, so it shows in the invoice's log and in your webhooks.
| What arrives | What Booked55 does |
|---|---|
| A paid payment that matches an invoice | Marks that invoice Paid, on the date of the payment, or today if GoHighLevel gives no date or one in the future. The payment note reads From GoHighLevel. |
| A paid payment that matches no invoice | Makes a one-time deal for that amount, with the General product and no tax, and one Paid invoice. The deal's note holds the amount and GoHighLevel's payment id, and the deal is marked Check the schedule for someone to look at. |
| A payment for someone not in Booked55 | Skips it as not_in_booked55. Only a lead makes a contact. |
| A status that does not mean paid, such as a refund or a partial payment | Skips it as payment_not_paid. Nothing changes. Record a refund yourself: see Refunds. |
| The same payment id again | Skips it as duplicate_payment, so a payment is never counted twice. |
| A paid payment with no id or no amount | Fails with inbound_payment_invalid. See Troubleshooting. |
These status words mean paid: paid, succeeded, success, successful, completed, complete, captured and received.
Which invoice a payment marks
- Booked55 finds the contact the same way it does for a lead: by GoHighLevel contact id, then email, then phone.
- It looks at the unpaid invoices on that contact's deals, leaving out cancelled deals.
- It keeps the ones for exactly the amount paid. A payment that names a currency code matches only invoices in that currency. A payment with no code matches any.
- It picks the Sent invoice with the earliest due date. If none is Sent, it picks the Draft with the earliest due date.
The amount must match the invoice's total. A paid amount that covers only part of an invoice matches nothing, so it makes a deal for someone to check.
Each payment shows on the Events tab as a Payment, with links to the contact and the invoice. If it marked the wrong invoice, an owner or a manager can click Undo paid.
9. Call and text through GoHighLevel
Each person chooses what a click on a contact's phone number does. Open your Profile and find Calls and texts. Pick one:
| Choice | What a click on a number does |
|---|---|
| My phone or computer | Opens the calling or texting app on the device you are using. |
| My Booked55 number | Calls or texts from your Booked55 number, inside Booked55. Offered once you have one. |
| GoHighLevel | Opens that contact in GoHighLevel in a new tab. You call or text them there. Offered once the connection has its Private Integration Token and Location ID. |
The choice is yours alone. A teammate can pick something else. It works the same in the phone app, where the contact opens in your phone's browser.
Booked55 finds the contact in GoHighLevel by the phone number you clicked. If several GoHighLevel contacts have that number, it opens the newest one. If nobody there has it, Booked55 adds the contact to GoHighLevel first, with their name, phone number, email and company, and then opens them. It never adds the same person twice. Adding a contact can start any GoHighLevel workflow of yours that runs when a contact is created.
After the call, your workflow sends it back, so the call, its recording and what was said land on your task in Booked55. A contact marked Do not call or Do not text is not opened for that.
10. Mass texts
A mass text is one text sent to many contacts from one of your GoHighLevel numbers. Each person gets it with their own details filled in. On the Contacts page, tick the contacts, or tick the header checkbox on your own list, and click Text on the selection bar. The button shows once GoHighLevel is connected with its token.
- From. The window always shows the number the text goes out from. If a GoHighLevel number belongs to you, it is picked. Otherwise it is your account's main number. You cannot send from a teammate's number.
- Write the text. Click First name, Last name, Full name or Company to add a detail. These are the same fields an email template uses, such as
{{contact.first_name}}. - Review. The next page lists everyone you picked, and says who is left out and why. Nothing has been sent yet.
- Read the warning. The page says how many texts can go right now. For the rest it says why they would wait and when they go. For example, it is a public holiday where some of your contacts are, or it is too early or too late there. Each contact's row says the same about that contact. A text that waits goes by itself when its time comes.
- Send now, or schedule. Tick the box that says everyone on the list agreed to get texts from you. Then click Send now, or click Schedule and pick a day and a time. The window shows the warning for the time you pick before you choose it. Booked55 keeps a record of who ticked the box and when.
A scheduled mass text starts by itself at its time. Until then you can click Cancel schedule. That makes it a draft again, so you can change it or pick another time.
Booked55 holds every mass text to these rules:
| Rule | What it means |
|---|---|
| Sending hours | Texts go out Monday to Saturday, 10 AM to 5 PM in each person's own time zone, and not on public holidays. Booked55 works out the time zone from the area code. Outside those hours the texts wait, and the page says when they go. |
| Opt-outs | Nobody marked Do not text gets one, and neither does anyone on Do Not Disturb in GoHighLevel. Booked55 checks GoHighLevel just before each text, and marks the contact Do not text in Booked55 too. |
| How to stop | Every text ends with your first name, your organization's name and “Reply STOP to opt out.” |
| Three in a day | One number gets at most three mass texts from your organization in any 24 hours. The fourth is left out. |
| Your account's daily limit | Booked55 counts every text your GoHighLevel account sent in the last 24 hours and stops at your limit. The limit starts at 500. The page shows how many texts are left. At the limit the mass text pauses, and it carries on by itself as room frees. An owner or a manager can click Change the limit to set what your GoHighLevel account allows. |
| One text per number | Two contacts with the same number get one text. A text is never sent twice. |
| Missing details | If the text uses a detail a contact does not have, such as a company, that contact is left out. |
| US and Canada | Only US and Canadian numbers get a mass text. One mass text takes up to 10,000 contacts. |
A contact who is not in GoHighLevel yet is added there, the same way as for a call. Each text shows under the contact's Texts in Booked55. Replies come back through your workflow.
Sending carries on in the background, so you can close the page. A large list takes a while, because the texts go out a few at a time. You can click Stop sending at any time. Texts already sent stay sent. Find every mass text under Outreach, on the Mass Texts tab.
The page of a mass text shows how it went. It says how many texts were sent, how many people texted back and how many asked to stop. It lists every reason someone got no text. Click any number to see the contacts behind it. When GoHighLevel refuses a text, that contact's row shows what GoHighLevel said. People who text back are counted when your workflow sends texts to Booked55, which is the Yes to texts in step 2.
Sent means GoHighLevel took the text. Whether the phone company delivered it shows in the contact's conversation in GoHighLevel.
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 | The contact's lead source, when your list has that name. A name that is not on your list is not added to it. The contact always gets a tag in the form Source: <contact source>. |
| Date created | When the lead came in, kept on the contact. See New contacts. |
| Company name and website | A company, matched by name in the assignee's book or created if none matches, linked to the contact. |
| Owner | Who a new contact goes to in Booked55. Read from the Custom Data key owner_email (value {{user.email}}), or else from the user GoHighLevel sends when it has one. See Who gets each contact. |
| Address | City, state, country, and postal code. |
| Do Not Disturb | The contact's Do not call, Do not text and Do not email flags, all three. |
| Note in the webhook | A note on the contact, if the payload carries one. |
| Full note history | One note per GoHighLevel note, each keeping the date it was written there. Only when a Private Integration Token is set. |
| Lead value | The value of the pipeline card when the event creates one, and the value of a one-time deal when the event puts the contact into a client stage. A value written with a currency sign or thousands separators (“$2,500.00”) is read as a number. |
| 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, which says how it reached Booked55. Its lead source says where the lead first came from. Each GoHighLevel note becomes a note on the contact in the Notes card, keeping the date it carried in GoHighLevel so it lands in the right place in the history. It is not logged as a task, so imported history does not inflate anyone's task counts, and it is marked Integration so a reader can tell it apart from a note your team typed.
A note is never imported twice. Booked55 remembers the GoHighLevel id of each note it has already stored, which is what keeps re-sends harmless — GoHighLevel re-sends a contact's whole note history on every stage change. For the occasional note that arrives without an id of its own, Booked55 falls back to comparing the text against the notes already on that contact.
The connection's settings decide where the contact lands: which pipeline and which stage. See Connection settings & stage mapping.
Ready to get started?
Create your free Booked55 account and start managing your sales pipeline in minutes.