A single card holding the credentials, the pipeline configuration and the first-sync action for a GHL-backed install. It shows the required token scopes inline, distinguishes credentials stored on the org row from legacy environment-variable credentials, and offers Disconnect only when the credentials are tenant-stored.
Also called: GHL · CRM connection · location id · private integration token
- 1Location ID and a Private Integration Token are entered and saved to the organisation row.
- 2The card lists the exact scopes the token needs: contacts read/write, opportunities read/write, conversations read/write and medias read/write.
- 3While the status call is in flight the card shows a stable checking skeleton instead of flashing an empty form.
- 4Environment-variable credentials are labelled as legacy single-tenant setup, and saving new values migrates the org to row-stored credentials.
Collapsed by default is with the stated reason: 'so nobody casually wanders into credentials they don't recognize'. The loading skeleton has its own note — it replaced 'the it shows nothing then fills in complaint'. Listing scopes inline exists because a token minted without the right scopes fails later, at sync time, where the cause is invisible.
- Credentials, pipeline settings and sync actions were spread apart.
- Tokens were created with wrong scopes and failed silently later.
- The card flashed an empty edit form before status loaded, implying disconnection.
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 →