The Integration Desk · Issue 2026

GoHighLevelYour CRM
sends the lead.
SlabOS sends
back the outcome.

Leads in your CRM pipeline land in SlabOS ready to quote. When a lead is sold or missed, SlabOS pushes it back as a contact and an opportunity — tagged, with the quote attached, labelled by showroom — so your campaigns run on what actually happened.

Sold & missed pushed back Tags added, never overwritten Showroom aware Syncs every five minutes

GoHighLevel is a product of HighLevel Inc. SlabOS is not affiliated with, or endorsed by, HighLevel — SlabOS connects to your own CRM account, on your instruction.

SlabOS · CRM sync
Pull: pipeline “Kitchen Leads” — 2 new opportunities → SlabOS leads
Stage: “Quote sent” → SlabOS stage “Quoted”
Sold: Nguyen kitchen — marked won in SlabOS
Push: contact matched by phone — slabos-sold slabos-plano
Push: opportunity “[Plano] Nguyen kitchen” — quote #, total & link attached
Watch:

Example sync — your pipeline, your stage names, your showrooms.

Chapter One
01
What flows in

Your pipeline,
ready to quote.

Pick one pipeline in your CRM. Every opportunity in it becomes a SlabOS lead — name, contact, phone, email, company and value ride along — and lands on the SlabOS stage you mapped it to. Won and lost in your CRM become won and lost in SlabOS.

If the person already exists as a SlabOS account, the lead is flagged as a possible duplicate for a human to merge — never silently merged.

Your CRM → SlabOS
OpportunityLeadkeyed to the opportunity, no duplicates on re-sync
Pipeline stageSlabOS stageyour map, stage by stage
Won / lostWon / lost stagealways, no mapping needed
Contact detailsOn the leadname, email, phone, company
Monetary valueLead valueuntil a real quote replaces it
Chapter Two
slabos-sold
contact tag
The lead was marked sold in SlabOS. Fire the review request, the referral ask, the “thank you” sequence.
slabos-missed
contact tag
The lead was marked lost. Run the win-back or the “still thinking it over?” sequence.
slabos-lead
optional
Turn on “every lead” and each SlabOS lead shows up in your CRM the moment it exists, then updates as it moves.
SlabOS custom fields
SlabOS Quote #SlabOS Quote TotalSlabOS Quote StatusSlabOS Quote LinkSlabOS StatusSlabOS Showroom
Created once on the opportunity when you connect. Build workflows on them like any other field.
02
What flows back

Sold or missed,
it’s in your CRM.

The moment a lead is marked sold or lost in SlabOS, it goes over as a contact and an opportunity in the pipeline you chose, at the stage you mapped, with the quote number, total and a link back to the quote.

The contact is matched by email or phone, so a customer your CRM already knows is updated, not duplicated. Tags are added, never overwritten. Cards SlabOS created stay current as the lead changes; cards born in your CRM keep your names.

Chapter Three
03
Showrooms

More than one
location? Labelled.

Shops with several showrooms get every lead labelled with the one it belongs to, three ways, so you can run campaigns per showroom without a second CRM account.

[Plano] Nguyen kitchenprefix on the opportunity name
slabos-planotag on the contact — old tag comes off if the lead moves
SlabOS Showroom = Planocustom field with the full location name

The prefix is yours to set per showroom — a short code like WGD-PLN works too.

How a lead’s showroom is decided
1
The location on its quote

Set by the showroom your rep is working in.

2
The account’s location

Existing customers already belong to a shop.

3
The customer’s city or state

Matched against each showroom’s service areas.

4
The assigned rep’s home shop

The final fallback.

No match means the lead goes over unlabelled. Better unlabelled than pinned to the wrong showroom.

Chapter Four
04
Set it up

Five minutes.
Owner login.

Everything lives on one card in SlabOS: Settings → Integrations → CRM. Connect, pick a pipeline, map the stages, decide what goes back. Then it runs on its own.

Connect
Map stages
Sync
1
Connect your CRM

Install SlabOS on the sub-account for your shop, or in your CRM go to Settings → Private Integrations, create one named SlabOS with Contacts, Opportunities, Custom Fields and Tags (read + write) and Locations (read), and paste the token and your Location ID into the card. It’s checked against your CRM before it’s stored, encrypted, and never shown again.

2
Pick the pipeline SlabOS follows

One pipeline. Its opportunities become SlabOS leads; SlabOS leads go back into it.

3
Map its stages to your SlabOS stages

Stage by stage. Won and lost land on your won and lost stages automatically; unmapped stages leave the SlabOS card where it is.

4
Choose what goes back

When sold, when missed, or every lead as it’s created. If you run more than one showroom, set a short prefix for each.

5
Save, then Sync now

The first pass runs immediately. After that it runs every five minutes, and the card shows the last sync and anything that needs your attention.

Owners, or a role with the Integrations permission, can connect. Disconnecting keeps every lead already in SlabOS; it just stops syncing.

Chapter Five
05
What stays where

Marketing there.
The shop here.

This is not a mirror of everything. Your CRM stays the marketing front door — contacts, nurture, texting, booking pages. SlabOS stays the system of record for the work — drawings, quotes, jobs, schedule, install, invoices. The sync carries the handful of facts each side needs from the other.

Your token, encrypted

Stored encrypted, never displayed again, never in any report or export.

Tags added, never replaced

Your existing tags and workflows are untouched. SlabOS only adds its own.

Loop-guarded

SlabOS remembers what it pushed and never re-imports its own cards as new leads.

Nothing about your shop is exposed

SlabOS calls your CRM on your instruction. No SlabOS data is published anywhere.

Running GoHighLevel?

Wire it to
the shop.

Book a demo and bring your pipeline. We’ll connect it live, map your stages, and you’ll watch the first lead land in SlabOS on the call.

Included for every shop · no add-on fee · see pricing

Questions
Do I have to rebuild my pipeline?

No. You pick the pipeline you already use and map its stages to SlabOS stages once. Your CRM keeps its stage names; SlabOS keeps its own.

Will it overwrite my tags or workflows?

No. SlabOS adds its own tags — slabos-sold, slabos-missed, slabos-lead and one per showroom — and never removes yours. Build workflows on those tags like any other.

What if the customer is already in my CRM?

The contact is matched by email or phone and updated, not duplicated. The opportunity is created in the pipeline you chose and linked to that existing contact.

I have several showrooms. Do I need a CRM account per showroom?

Not for this. One connected account is enough: every lead is labelled with its showroom by a prefix on the opportunity name, a tag on the contact and a custom field, so you can segment campaigns per showroom. The showrooms come from your SlabOS shop locations.

How fast does it sync?

Every five minutes in both directions, or immediately with Sync now on the card. The card shows the last sync, what moved, and anything that needs attention.

What does my CRM need to allow?

Contacts, Opportunities, Custom Fields and Tags (read and write) and Locations (read). Nothing else. SlabOS asks for the minimum and stores the credential encrypted.

Is SlabOS affiliated with HighLevel?

No. GoHighLevel is a product of HighLevel Inc. SlabOS is not affiliated with, partnered with, or endorsed by HighLevel. SlabOS connects to your own CRM account on your instruction.

Keep exploring
Pipeline & CRM Website quoting Call intelligence The mail engine Customer portal Product tour Pricing
We’re on the floor · TISE 2027
Mandalay Bay, Las Vegas · Feb 2–4
Come say hi