GoHighLevel (GHL)

Connect

Multi sub-account

Repeat for each sub-account. The ghl spoke federates across all configured sub-accounts — agents see them as one search surface, scoped by sub-account where the answer needs to be.

BAA

Per sub-account, toggle "BAA on file with GHL for this sub-account". When on, the spoke is treated as safe for that sub-account; otherwise scrubbed.

What you can do once connected

• Every workflow can call a team via team GHL webhook.
• The exec heads (Jordan, Alex, Taylor) can read + write GHL in chat and the War Room.
• Voice AI workflows can be enriched mid-call via Ambrose tool calls.

What the ghl spoke can actually do

Once connected, any agent, team, or exec head with the ghl spoke enabled can do all of this in plain English — no IDs to copy, the spoke resolves names to IDs for you:

• Contacts — search, read, create/upsert, update, add/remove tags, add notes: ghl_contact_search, ghl_contact_get, ghl_contact_upsert, ghl_contact_update, ghl_contact_add_tags, ghl_contact_add_note.
• Pipelines & opportunities — list pipelines/stages, create opportunities, move a card between stages, set status: ghl_pipelines_list, ghl_opportunities_list, ghl_opportunity_create, ghl_opportunity_move_stage, ghl_opportunity_set_status. See the worked example: add context + move a contact through a pipeline →
• Conversations — list threads, read messages, send SMS/email: ghl_conversations_list, ghl_conversation_messages, ghl_send_message. Worked example: messages today + follow-up →
• Tasks, calendars, workflows, custom fields/values, social planner, users, Voice AI — ghl_task_create, ghl_calendar_book, ghl_workflow_enroll, ghl_custom_field*, ghl_social_post_create, and more.

Write actions (send message, move stage, create task, …) default to Ask — they stage for your approval in the War Room. Flip them to Allow on the Tools page to run unattended.