Wire-by-wire connection status

Instead of one 'connected' light per provider, each individual wire — location id, token, texting, email, pipeline ids — reports its own state with a masked value and a fix.

What it is

loadOrgFacts returns a connections map: for GoHighLevel, five separate points (sub-account id, private integration token, texting set up inside GHL, email set up inside GHL, pipeline ids); for Twilio, three (platform credentials, phone number, A2P registration); for Mailgun, two (platform credentials, verified sending domain). Each carries connected true/false, a masked detail, and a sentence naming what to do about it.

Also called: is GoHighLevel actually connected · what's missing · integration health

See it
Wire-by-wire connection status
🔒ridgelinepostframe.com/project/provid659
Hobby Shop
Framing · on schedule
A checklist panel: five GoHighLevel rows each with a dot, a masked value, and (when red) a one-line fix. Rendered in the comms console — src/components/settings/CommunicationsTab.tsx and src/components/settings/comms/PhoneChannelTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1One read pulls the organizations row, the account's bindings, the platform bindings, and org_ghl_config.
  2. 2Each wire is evaluated independently and its value masked (first six and last four characters, or 'stored, encrypted').
  3. 3A sending domain only counts as verified once it is not the shared root and not marked pending.
  4. 4The panel renders one row per wire with its own dot.
Why we built it

The interface comment is the argument: '"GoHighLevel" is not one connection — it's a location id, a private integration token, and whatever was set up inside GHL for texting and email. Collapsing them into one boolean is how an account with a location but no token reads as "connected" right up until a send fails.' There is a second correction recorded there too: connection state was being read from org_ghl_config, 'which holds only the pipeline IDs and is populated for almost nobody; reading connection state from it reported a fully connected tenant as having no token.'

The problem
  • A single connected boolean hid a half-configured integration until the first failed send.
  • Connection state was read from the wrong table and reported false negatives.
Sound familiar?
What you get
The exact missing wire is named, with the fix, before anyone tries to send.
Secrets are shown masked, never in full, on the status surface.

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 →