Integrations setup done for you

The agency wires a builder's back-end integrations from the panel — auto-detecting the pipeline, mapping stages by name — and controls which integrations that builder ever sees.

What it is

A tab holding integration status, the token and location fields, per-integration visibility switches for the customer's own settings screen, and feature grants. It exists because the customer should never have to touch this layer at all.

Also called: connect my systems · integration setup · I don't want to set up an API key · wiring · hide integrations

See it
Integrations setup done for you
New lead 3
Marlin Hoover
$41k
Delia Yoder
$24k
Contacted 2
Sutter Kline
$51k
Ronan Petsch
$49k
Estimate 2
Ivy Brubaker
$63k
Gideon Alt
$60k
Sold 3
Marlin Hoover
$18k
Delia Yoder
$69k
Sutter Kline
$68k
The Integrations tab: connection stats, masked token and location fields with reveal/copy, the stage-mapping result ('12 of 12 mapped'), and the visibility toggles. Sample data — no customer information appears here.
How it works
  1. 1Provisioning creates the sub-account from a template snapshot with the pipeline and stages pre-loaded.
  2. 2Staff open that sub-account, create the integration token (there is no API for that step) and paste it here.
  3. 3On save the platform auto-detects the sales pipeline, maps every stage by name and seeds the configuration — sync goes live with zero customer action.
  4. 4The location id is editable, because the provisioned value can be missing or wrong; the connect route identity-verifies the token against whatever id is submitted.
  5. 5Visibility switches hide an integration inside the customer's settings without disconnecting it.
  6. 6Feature grants are the opposite polarity — they give a customer something they did not have, such as the 3D builder.
Why we built it

The panel's header states the posture: 'WE wire GoHighLevel for the tenant (they never see or hear about GHL).' The editable location id carries its incident: 'the provisioned value can be missing or — as the cross-tenant incident proved — wrong, and the operator needs a way to set it.' Visibility and grants are kept distinct on purpose: 'visibility hides something they already have, a grant gives them something they didn't.'

The problem
  • Integration setup asked a builder to do work only the vendor can do safely.
  • Stage mapping by hand is error-prone and silently breaks sync.
  • A wrong location id could point one customer's sync at another's data.
  • Customers saw settings for integrations they had never signed up for.
Sound familiar?
What you get
Your integrations are live without you touching a token.
Stages map themselves by name instead of by a manual table.
Your settings screen only shows the things you actually use.
What's inside

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →