Audio is played by ElevenLabs, which loads only when you press the button. Privacy Policy

Connection settings & stage mapping

Every connection has its own settings. Its name and its on/off switch are at the top of the connection's page. The Settings tab holds the tags, the default pipeline, which Booked55 stage each GoHighLevel stage lands on, and who gets each lead. The webhook URL, the Location ID and the Private Integration Token are on the Setup tab.

Settings reference

SettingWhat it does
NameAt the top of the page. Click it to change it. It is the connection's name in the Integrations list.
Receiving leadsThe large switch at the top of the page. Off, it reads Paused: Booked55 answers 404 to GoHighLevel and stores nothing, so leads sent while it is off are lost.
TagsAdded to every imported contact, on top of the tags carried over from GoHighLevel.
Where leads goA switch with two sides, and only one is used. Default pipeline: every lead goes to one pipeline and stage. Stage mapping: each lead goes to the Booked55 stage picked for its GoHighLevel stage. Saving one side turns the other off. See below.
UsersWho each GoHighLevel user's leads go to. Nothing to set. Needs the token. See Who gets each contact.
Private Integration TokenOn the Setup tab. Optional, but Stage mapping, Users and full note history need it. See below.

Who gets each contact

The workflow's Webhook action carries the owner in three Custom Data rows: owner_email, owner_first_name and owner_last_name. GoHighLevel does not always send the owner on its own, so these make sure it arrives. Booked55 gives a new contact to the user that owner matches, checked in this order:

  1. The same email address.
  2. The same full name. Capital letters, accents and punctuation do not matter.
  3. The same first and last name, so a middle name on either side does not matter.

A step counts only when exactly one user matches. When the owner matches nobody, or two users share the name, the contact goes to the person who set up the connection. Each event's details show which step matched, under Owner.

With the token saved, the Users section on the Settings tab lists every GoHighLevel user and the Booked55 person their leads go to, before any lead arrives. To send someone's leads to a different person, give them the same email address in both.

A contact that is already in Booked55 keeps its owner, even when GoHighLevel names someone else later. To give it to someone else, change its owner in Booked55.

When a contact already exists

Before it creates anything, Booked55 looks for a matching contact in your workspace, in this order:

  1. The GoHighLevel contact id, which Booked55 remembers on the contact after the first import.
  2. The email address, compared lower-cased.
  3. The phone number, compared by digits in a few common formats.

The phone rule cuts both ways: two GoHighLevel contacts that share a number, such as an office line, are one contact to Booked55. Give them different numbers in GoHighLevel, or set the connection to Create another, if they must stay separate.

The app does not show a choice for this: a match is updated and appended to. The in-app assistant can switch a connection to Skip or Create another if you ask it.

  • Update and append (default) — Fills in fields that are empty, the lead source among them, adds new tags and phone numbers, adds any notes it has not seen before, and moves the pipeline stage if a mapping applies. It never overwrites a field that already has a value, never changes the contact's email or assignee, and never touches a note that is already there.
  • Skip — Records the event and changes nothing. The event is marked skipped with the reason duplicate_contact.
  • Create another — Creates a new contact every time, even when one matches. Use it only if every GoHighLevel opportunity should be its own Booked55 contact.

Where leads go: default pipeline or stage mapping

On the Settings tab, Where leads go has two sides. Only one is used, and saving one turns the other off, so a lead never has two places to go.

  • Default pipeline — Every lead goes to the pipeline and stage you pick. Pick both, then click Save changes.
  • Stage mapping — Each lead goes to the Booked55 stage picked for its GoHighLevel stage, and its card follows the opportunity when it moves in GoHighLevel.

Stage mapping needs the Private Integration Token, because Booked55 reads your GoHighLevel pipelines and stages with it, so nothing is typed by hand. It also needs a second workflow in GoHighLevel.

The stage workflow

The lead workflow from Connect GoHighLevel sends a lead when it reaches your hand-off stage. A move to any other stage reaches Booked55 only through a second workflow, Send stage changes to Booked55. Its trigger is Pipeline Stage Changed on your pipeline with no stage filter, and its Webhook action posts to the same URL with one Custom Data row: booked55_event = stage_changed. Turn on Allow Re-entry in its Settings: without it, GoHighLevel runs the workflow only the first time each contact moves.

Booked55 asks for this workflow the first time you open Stage mapping, with a Copy prompt button for GoHighLevel's Workflow AI Builder. Once the workflow is published, click Yes, I turned on the workflow and it is published in GoHighLevel. After that, Copy prompt again stays above the stages.

An event from the stage workflow only moves a card:

  • It moves the contact's card to the mapped Booked55 stage, and never changes the contact's details.
  • A contact that is not in Booked55 is skipped as not_in_booked55. The lead workflow creates contacts; this one never does.
  • A GoHighLevel stage with no mapping is skipped as stage_not_mapped, and the card stays where it is.

Mapping the stages

  1. Save the token on the Setup tab.
  2. On the Settings tab, under Where leads go, pick Stage mapping.
  3. Build the stage workflow, then confirm it is published (above).
  4. Each GoHighLevel pipeline has its own tab. Beside each stage, pick a Booked55 stage, or leave it on Not mapped.
  5. Click that tab's Save button. Each pipeline saves on its own.

Map your hand-off stage too: with stage mapping on, a lead that arrives at a stage left Not mapped comes in without a pipeline.

Leads carry the pipeline and stage by name, so a mapping is kept by name too. If you rename or delete a stage in GoHighLevel, its old mapping is listed under the table so you can remove it, and the renamed stage appears in the table to map again.

How a stage is resolved

  1. With Stage mapping, the contact goes to the Booked55 stage picked for its GoHighLevel pipeline and stage.
  2. With a default pipeline, the contact goes there.
  3. Otherwise, or at a stage left Not mapped, the contact is imported with no pipeline item. It exists in Contacts but is not on any pipeline.

Already on a pipeline

A contact can be on only one pipeline at a time in Booked55. When a matched contact already has a pipeline item, the incoming event moves it to the stage the mapping resolved to. The rest of the update applies as well.

Client stages need a value

A client stage is a Booked55 stage with the Client stage type. Entering one marks the contact as a client and creates a deal, and a deal needs a value. When a mapped stage or the default stage points at a client stage, every event that puts a contact there must carry the opportunity's Lead Value above 0 (sent as lead_value). That applies both when the event creates the pipeline card and when it moves an existing card in.

  • With a Lead Value — The card gets that value, the contact is marked as a client, and one one-time deal is created with the same value. GoHighLevel does not say how the client pays, so the deal is marked Check the schedule for someone to set the real schedule.
  • Without one, or with 0 — The event fails with inbound_value_required_for_client_stage and nothing from it is imported: no contact, no pipeline card, no deal. The error names the client stage it was refused for.
  • Moving a card that already has a value — Allowed without a Lead Value. The deal takes the value already on the card.
  • A card already in that client stage — An event that names the same stage again leaves the card where it is and creates no second deal, with or without a value.

The Settings tab marks each mapped stage that is a client stage, and shows this rule under the table, or under the default pipeline when its stage is one. A stage that only passes a card on to a client stage through Move immediately automation is not checked here: that deal takes the card's value, as it does for a card moved by hand.

Worked example

Your GoHighLevel pipeline is called Sales and the stage that should hand a lead to sales is Appointment Booked. In Booked55 those leads belong on the Sales Process pipeline at the Appointment Set stage. Under Where leads go, pick Stage mapping, build the stage workflow, then on the Sales tab pick Sales Process › Appointment Set beside Appointment Booked:

GoHighLevel stageBooked55 stage
Appointment BookedSales Process › Appointment Set

When an opportunity in the Sales pipeline reaches Appointment Booked, the workflow fires and the contact appears on Sales Process at Appointment Set, assigned to the Booked55 user who owns the opportunity in GoHighLevel, or to the person who set up the connection when that owner matches nobody. When the opportunity later moves to another mapped stage, the stage workflow moves the card too. If you later add a second GoHighLevel pipeline, it gets its own tab with its own stages to map.

Private Integration Token

Leads import without a token, but five things need one:

  • Stage mapping: Booked55 reads your GoHighLevel pipelines and stages with it.
  • Users: Booked55 reads your GoHighLevel users and shows who gets each one's leads.
  • Full note history: the webhook carries at most one note. With the token, Booked55 pulls every note on the contact from GoHighLevel and adds each one to the contact's Notes, keeping the date it was written in GoHighLevel.
  • Call recordings: Booked55 finds and plays the recording of a call your workflow sent from GoHighLevel with it.
  • Your workflow: when you answer Yes to Did you create the workflow and publish it?, Booked55 checks that it is published.
  • Calling and texting through GoHighLevel: a click on a contact's phone number opens that contact in GoHighLevel, and a mass text goes out from one of your GoHighLevel numbers. See Call and text through GoHighLevel.

Select every scope when you create the token. A token made earlier with only some scopes still does what those scopes allow. To give it the rest, open the integration under Private Integrations in GoHighLevel and select them all.

  1. 1

    Open Private Integrations in GoHighLevel

    On the connection's Setup tab, the Private Integration Token section has an "Open Private Integrations in GoHighLevel" link that goes straight to that page for your sub-account. Click "Create new Integration".

  2. 2

    Name it and select every scope

    Give the integration a name such as "Booked55". Under scopes, select all of them. With every scope selected now, you never have to come back and add one when Booked55 learns to do something new. Booked55 reads contacts and their notes, your users, your pipelines and stages, call recordings, your texts if you said yes to them, your phone numbers and the list of your workflows. It adds a contact or sends a text in GoHighLevel only when someone on your team asks it to: by opening a contact there from Booked55, or by sending a mass text.

  3. 3

    Copy the token

    GoHighLevel shows the token when the integration is created. Copy it.

  4. 4

    Paste it into the connection

    In Booked55, open the connection. On the Setup tab, paste the token into the Private Integration Token section and click Save token. Booked55 checks it with GoHighLevel straight away and tells you if anything is wrong.

The Location ID is the code after /location/ in the GoHighLevel address bar. Booked55 asks for it when you create the connection, and you can paste the whole address: Booked55 keeps only the code. A connection made before that learns it from its first lead. It sits on the connection's Setup tab, under the webhook URL, with Replace beside it. With the Location ID, the Setup tab links straight to Workflows and Private Integrations in your sub-account.

The token is stored encrypted and is never shown again once saved. Booked55 reads with it, and writes to GoHighLevel only when someone on your team asks: it adds a contact that is not there yet, and it sends the texts of a mass text. Once saved it shows as dots in a locked field. To change it, click Replace token, paste the new one and click Save token. Remove token deletes it.

To fix a mistyped Location ID, click Replace beside it, paste the right one and click Save; nothing else changes. A token belongs to one sub-account, so a Location ID from another sub-account needs a token from that one too. Booked55 asks for it right there and saves both together. Build the workflow in the new sub-account as well.

If the token is refused

MessageWhat to do
GoHighLevel did not accept this tokenThe token is wrong or was deleted. Copy it again from Private Integrations (the link in the Setup tab's Private Integration Token section).
GoHighLevel accepted the token but would not allow thisThe token is missing a scope. Open the integration under Private Integrations in GoHighLevel, select every scope, and check the Location ID is the same sub-account's.
GoHighLevel did not find that Location IDCopy the Location ID again from the address bar, after /location/.
Could not reach GoHighLevelTry again in a minute.

For what happens to each event after these settings are applied, see Event log & troubleshooting.

Ready to get started?

Create your free Booked55 account and start managing your sales pipeline in minutes.