GoHighLevel

Connect a GoHighLevel sub-account and Preb keeps your CRM in sync with every booking automatically. Leads, booked calls, reschedules, cancellations, no-shows, and call outcomes all flow into GoHighLevel as contacts, appointments, notes, and pipeline opportunities — and changes you make in GoHighLevel flow back to Preb, so the two stay in agreement without anyone copying data by hand.

It's a two-way, native integration: no Zapier, no CSV exports. Preb becomes the scheduling engine in front of your GoHighLevel pipeline, and — because Preb is where your ad-click IDs live — a deal you mark won anywhere fires the Purchase conversion back to your ad platforms, closing the attribution loop.

Adding the app

Prerequisites

• A GoHighLevel sub-account (location) you can install a marketplace app into. Agency owners install it into the specific sub-account they want synced.
• A Preb workspace where you are an admin — connecting and configuring GoHighLevel is an admin-only action.

Connect your GoHighLevel sub-account

Set up what syncs

After connecting, open Integrations → GoHighLevel to configure the sync. Each card is optional — turn on only what you need:

You can also override any of these per event type from the GoHighLevel tab in the event-type editor (it appears once a connection is active).

Troubleshooting

Still stuck? See our contact & support guide and we'll help you sort it out.

Using the app

Once GoHighLevel is connected, these features work automatically based on what you enabled. Each one lists what it does and what needs to be in place first.

Leads and contacts sync as they come in

• Use case: A visitor completes the first step of your booking form. Preb upserts them as a GoHighLevel contact (deduped by email or phone), adds your configured tags, sets the source, and fills any mapped custom fields.
• Prerequisites: Contact sync is on. Tags are added, never overwritten, so your existing GoHighLevel tags are safe.
• Optional — unfinished leads too: Workspace owners can additionally turn on Send unfinished leads to your connected CRM (Settings → Data retention). Visitors who started typing into the form but never submitted are then pushed to GoHighLevel about two hours later. Leads synced this way are kept (they're in your pipeline now) instead of being auto-deleted after 30 days — and they're your responsibility under privacy law like any other CRM contact.

Bookings become appointments

• Use case: A call is booked. Preb creates a GoHighLevel appointment on the chosen calendar, assigned to the mapped host, with the meeting link as the location. Reschedules update the same appointment in place; cancellations and no-shows update its status.
• Prerequisites: A calendar is selected (Preb's auto-created "Preb Bookings" calendar is the default).

The pipeline follows the call

• Use case: As a lead moves from booked to showed to won, Preb moves a single opportunity through your pipeline stages and records the deal value on a sale. There's always one opportunity per contact per pipeline — no duplicates.
• Prerequisites: A pipeline is selected and its stages are mapped to Preb's lifecycle stages. Unmapped stages are simply skipped.

Two-way sync keeps both sides honest

• Use case: Someone edits a contact, moves an opportunity, or cancels an appointment in GoHighLevel — Preb picks it up and updates its own records, without echoing the change back and causing a loop.
• Prerequisites: The relevant sync-back toggles are on. Contact merges take name and phone from GoHighLevel (your CRM of record) and never touch a contact's ad-attribution data.

Won in GoHighLevel fires your ad conversion

• Use case: You drag an opportunity to won in GoHighLevel. Preb records the sale and fires the Purchase conversion to your connected ad platforms — using the ad-click IDs it captured at booking time — so revenue is attributed even when the deal closes in the CRM. It fires exactly once, whether you close the deal in GoHighLevel or in Preb.
• Prerequisites: Opportunity sync-back is on, and you've connected an ad platform (e.g. Meta) in Preb's tracking settings.

Availability respects GoHighLevel calendars

• Use case: A host already has appointments or blocked time on their GoHighLevel calendar. Preb treats that time as busy so it's never offered as a bookable slot — no double bookings across the two systems.
• Prerequisites: The host is mapped to their GoHighLevel user and the Use GoHighLevel calendars for availability toggle is on for them.

Owner-based routing

• Use case: A returning lead who already has an assigned owner in GoHighLevel books again. Preb offers only that owner's availability, so the relationship stays with the person who owns it. If the owner isn't available or isn't mapped, Preb falls back to normal round-robin.
• Prerequisites: Owner routing is enabled on a round-robin event type, and the host is mapped to their GoHighLevel user.

Conversations logged in one thread

• Use case: Every confirmation, reminder, reschedule, and cancellation email or text Preb sends to the invitee is mirrored into that contact's GoHighLevel conversation, so your team sees the full history where they already work. Preb stays the sender — this only records a copy.
• Prerequisites: Conversation logging is on (it's on by default for newly connected workspaces).

Permissions Preb requests (and why)

When you connect, GoHighLevel asks you to authorize a set of scopes. Preb requests only what the features above need — nothing is used for advertising, resale, or profiling, and Preb never reads data it doesn't act on. Here is every permission and exactly what it's for.

Data & privacy

• What Preb stores: the connection's encrypted access/refresh tokens, the location id, and the mapping choices you configure (which calendar, pipeline, fields, and team members to use). It does not copy your GoHighLevel contact database into Preb.
• Direction of data: Preb writes booking and outcome data into GoHighLevel, and reads back only the specific changes it needs to stay in sync (a contact edit, an opportunity status, an appointment change). A contact's ad-attribution data is never overwritten by a sync-back.
• Removing your data: disconnecting from Preb, or uninstalling the app in GoHighLevel, stops all syncing immediately and removes the stored connection and its tokens. Records already written to your GoHighLevel account are yours and are left in place.

Removing the app

You can disconnect from either side.

From Preb

Go to Integrations → GoHighLevel and click Disconnect. Preb stops syncing and removes the stored connection.

From GoHighLevel

Uninstall the Preb app from your sub-account's marketplace/installed-apps screen. GoHighLevel notifies Preb, which immediately marks the connection as needing a reconnect and stops syncing.

What removing the app does

• Preb stops creating and updating GoHighLevel contacts, appointments, and opportunities for future bookings, and stops accepting changes from GoHighLevel.
• Contacts, appointments, and opportunities already in GoHighLevel stay there — disconnecting doesn't delete anything in your CRM.
• Your Preb-side settings (calendar, host mapping, field and pipeline mapping) are kept, so reconnecting the same location picks up exactly where you left off — the "Preb Bookings" calendar is reused rather than recreated.