A platform-gated endpoint that stores the token and location, fetches the location's pipelines with the new credentials, auto-picks the sales pipeline (name match, then single, then first), builds the stage map by name-matching CRM stages onto the internal stage ids, and upserts org_ghl_config so is_connected flips true. A GET returns connection status including the template snapshot's push state.
Also called: auto-map pipeline stages · no dropdowns · connect sub-account · operator connect
- 1Operator opens the tenant's Integrations panel and pastes the private integration token.
- 2The token is verified against the location.
- 3Pipelines and stages are fetched server-side with the caller-supplied credentials.
- 4The sales pipeline is auto-selected and sales_stage_map is built by normalised name match.
- 5org_ghl_config is upserted, is_connected flips true, and every sync lights up.
The route header spells out the intent: 'Platform-side GHL connect for a tenant — WE wire the integration, the builder never touches (or even knows about) GoHighLevel', with the auto-mapping justified because 'the template snapshot guarantees it exists with our 9 stage names'. The panel also carries feature grants, and the header is careful about why they stay separate: 'visibility HIDES something the tenant already has; a grant GIVES something they did not.'
- Stage mapping was manual and error-prone.
- A tenant could be connected but with no pipeline configured, so leads never arrived.
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 →