GoHighLevel Integration
Connect GoHighLevel via a webhook workflow so completed calls flow into CloseIntel automatically.
Connecting GoHighLevel
GoHighLevel (GHL) is a CRM and marketing platform. Connect it to CloseIntel as an Auto-Sync Integration so that when GHL completes a call, the recording is sent to CloseIntel, transcribed, and queued for AI analysis in Intel (the Call Analyzer). The connection works by sending GHL call data to a CloseIntel webhook from a GHL workflow.
Setup
The setup wizard walks you through four steps. Open Settings → Integrations, click the GoHighLevel tile, then Connect:
- Webhook Secret — CloseIntel generates a secure secret. Copy it; you'll use it as the Bearer Token in GHL.
- Configure Workflow — CloseIntel generates your Webhook URL. In GHL, go to Automation → Workflows and create a workflow with the Call Status Changed trigger filtered to Completed. Add a Custom Webhook (POST) action, paste the Webhook URL, set auth to Bearer Token with your secret, and paste the JSON Body the wizard provides. Save and publish the workflow.
- Verify — CloseIntel waits for a test webhook from GHL (up to 2 minutes). Trigger a test call or run your workflow to confirm it's working.
- Done — the integration is active.
GoHighLevel call recordings are transcribed using AssemblyAI after the recording arrives, then queued for analysis.
How it works
Once connected:
- When a GHL call is marked Completed, GHL sends the recording to CloseIntel via your workflow webhook.
- CloseIntel transcribes the recording and queues it for AI analysis.
- Imported calls appear in your call list (History in the sidebar) with a GoHighLevel source label.
Managing the integration
From the GoHighLevel tile in Settings → Integrations you can:
- Auto-analyze new calls — toggle automatic analysis on or off.
- Filter by meeting title keywords, set a minimum call duration, and skip voicemails to control which calls are analyzed.
- View Activity — see recent webhook events, including any failures.
- Rotate webhook URL — generate a fresh URL (you'll need to update it in your GHL workflow).
- Disconnect — stop syncing at any time.
Troubleshooting
- No webhook received during Verify: confirm the workflow is published (not just saved), the Webhook URL is pasted correctly, and the Bearer Token matches your secret.
- Trigger too restrictive: make sure the Call Status Changed trigger is filtered to Completed.
- Missing rep info: the JSON Body must include the user/rep email and name fields from the wizard so calls map to the right rep.
- Missing recording: confirm call recording is enabled in GHL for the calls you want analyzed.
Tips
- The integration works best when call recording is enabled for all inbound and outbound calls in GHL.
Related articles
Was this article helpful?