Integrations

One admin tab holding every service this company is connected to — CRM, estimating, card payments, accounting — plus its lead sources.

What it is

Settings → Integrations is a shell with two views: Connected services (GoHighLevel, SmartBuild, Stripe, QuickBooks, plus the estimate engine choice and the danger zone) and Lead Sources (Facebook and Google connections, web forms, Zapier and custom webhooks). Credentials are stored per tenant, shown masked, and revealable field by field.

Also called: connect my accounts · api keys · connected services · hook up quickbooks · integrations tab

See it
Integrations
Area
Integrations
Group
Connected services
System
Integrations
Solves
2 named problems
01A status call reports, per service, whether it is connected, whether the credentials come from stored rows or environment variables, and masked values.
02Each service card offers Update and, where the credentials are tenant-stored, Disconnect.
03The platform owner can hide any service's card without touching connection state.
The Integrations tab with the collapsed GoHighLevel card, SmartBuild, Stripe and QuickBooks cards each with a Connected badge. IntegrationsTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1A status call reports, per service, whether it is connected, whether the credentials come from stored rows or environment variables, and masked values.
  2. 2Each service card offers Update and, where the credentials are tenant-stored, Disconnect.
  3. 3The platform owner can hide any service's card without touching connection state.
  4. 4The whole tab can sit behind an optional PIN.
  5. 5The legacy Lead Sources deep link opens the second sub-tab.
Why we built it

The shell comment quotes v3: 'lead sources is like a Facebook and Google integration… it would make more sense under the integrations tab' — which also retired the Leads category. Putting every connection in one tab means the answer to 'what is this software plugged into' is one screen rather than four.

The problem
  • Connections were configured in different places with different conventions.
  • There was no single view of what a company had connected.
Sound familiar?
What you get
One screen answers what is connected and whether it is working.
Credentials can be verified and copied without leaving the app.
What's inside
GoHighLevel connection
Everything GoHighLevel — location id, integration token, pipeline mapping and first sync — inside one collapsible card, collapsed by default.
Pipeline and stage mapping
Choose which CRM pipeline feeds the platform and map each internal stage to a CRM stage, with a paste-the-id escape hatch when the dropdown can't see a pipeline.
Run first sync
One button that proves the credentials and pipeline ids are right by pulling fresh counts of contacts and opportunities, in milliseconds.
SmartBuild login
Store the company's SmartBuild username and password so estimates and job data can be pulled into the platform.
Stripe card payments setup
Paste your own Stripe key so customers can pay invoices by card — the funds and the fees are yours, and the webhook creates itself.
QuickBooks connection
QuickBooks Online connects by OAuth rather than pasted keys, so it lives in its own card with its own status and item mapping.
Reveal and copy a stored credential
Stored keys render masked with a per-field eye to reveal and a one-click copy, and the page says out loud who can see them.
Hide a service without disconnecting it
The platform owner can hide any connected-service card from a tenant's Settings without changing whether it is connected or how it syncs.
Agency-granted 3D builder access
Whether an account may even see the in-house 3D builder is an agency grant; the tenant's own engine choice sits underneath it.

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 →