> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vapify.agency/llms.txt
> Use this file to discover all available pages before exploring further.

# GoHighLevel

> Map GHL sub accounts to Vapify sub accounts, sync recordings, and trigger calls from workflows.

## Overview

The GoHighLevel (GHL) integration wires your existing Vapify sub accounts and assistants into GHL, so calls, recordings, and workflows stay in sync, without exposing your prompts, provider configs, or pricing to clients.

## Prerequisites

* Sub accounts already set up in Vapify with assigned assistants and pricing
* A GoHighLevel account with marketplace access

## Steps

1. In GHL, open the marketplace, find **Vapify Voice AI**, click **Install**, and approve permissions.

<img src="https://mintcdn.com/vapifybykanzucode/A3O19gLqD2_WDy2-/images/ghlinstallation.png?fit=max&auto=format&n=A3O19gLqD2_WDy2-&q=85&s=271ea3b9c0a0bf72cc6c64fd727579bd" alt="GoHighLevel Marketplace showing Vapify installation" width="1366" height="669" data-path="images/ghlinstallation.png" />

2. Click through to Vapify login, sign in with your agency account, and approve the connection.

<img src="https://mintcdn.com/vapifybykanzucode/A3O19gLqD2_WDy2-/images/ghlauth.png?fit=max&auto=format&n=A3O19gLqD2_WDy2-&q=85&s=ad16fd3c2aefe4f5fc13f3338b8a3f88" alt="Vapify authentication screen during GHL install" width="1366" height="669" data-path="images/ghlauth.png" />

3. For each client, pick a **GHL subaccount** and map it to the matching **Vapify subaccount**. Repeat for all clients and save.

<img src="https://mintcdn.com/vapifybykanzucode/A3O19gLqD2_WDy2-/images/ghlmapping.png?fit=max&auto=format&n=A3O19gLqD2_WDy2-&q=85&s=542b82ff78acde17965247074fa45bac" alt="Map GoHighLevel sub accounts to Vapify sub accounts" width="1366" height="668" data-path="images/ghlmapping.png" />

4. To trigger outbound calls from a workflow, add the **Make Phone Call (Vapi Voice AI)** action, choose the assistant from the mapped sub account, and target the workflow contact.
5. Test one inbound and one outbound call, and confirm the recording attaches to the correct GHL contact.

<img src="https://mintcdn.com/vapifybykanzucode/A3O19gLqD2_WDy2-/images/ghlcallrecordingsaved.png?fit=max&auto=format&n=A3O19gLqD2_WDy2-&q=85&s=c4ce16f7bd40cb2bfe4163dac00fedc0" alt="Call recording attached to a GHL contact" width="1366" height="669" data-path="images/ghlcallrecordingsaved.png" />

<Note>
  Map one GHL subaccount to exactly one Vapify sub account. This keeps pricing and data isolated between clients, the same isolation principle covered in [Understanding Sub Accounts](/running-your-agency/understanding-sub-accounts).
</Note>

## What syncs automatically

* **Inbound calls**: matched to the GHL contact by phone number; recording, duration, and timestamp attach automatically.
* **Outbound calls**: triggered by workflow, batch, or direct call; recording attaches to the originating contact.
* **What GHL users see**: a **Voice AI Assistants** menu, plus **Call summary** and **Call logs** scoped to the mapped sub account.

<img src="https://mintcdn.com/vapifybykanzucode/A3O19gLqD2_WDy2-/images/ghlvapifydashboard.png?fit=max&auto=format&n=A3O19gLqD2_WDy2-&q=85&s=dc9401f3f5d96f462b097918c606dff5" alt="Voice AI Assistants dashboard inside a mapped GHL sub account" width="1366" height="668" data-path="images/ghlvapifydashboard.png" />

## What stays hidden from clients

Provider costs and prompts are never exposed. GHL users see only the assistants and prices set in the mapped Vapify sub account.

## Troubleshooting

* **Recordings not showing**: check the subaccount mapping, confirm the contact exists with a matching phone number, and confirm the call completed.
* **Voice AI menu missing**: confirm the subaccount is mapped and the user has relogged in.
* **Workflow action fails**: test the assistant directly in Vapify, verify the mapping, and confirm the contact's phone number is valid.
* **Wrong contact attached**: check for duplicate phone numbers in GHL and standardize number formatting.

## Related Articles

* [Understanding Sub Accounts](/running-your-agency/understanding-sub-accounts): the isolation model this integration relies on
* [Call Logs](/running-your-agency/call-logs): the Vapify-side call history behind GHL's synced view
* [AI Assistants](/running-your-agency/ai-assistants): assistants that become callable through GHL