GoHighLevel integration

Send call recordings from GoHighLevel (GHL) into Call Analytics, get back a scored report, and surface it inside GHL. No code required for the basic path — it's a GHL Workflow webhook action pointed at our inbound endpoint.

1. Get an API key

In the app, open Company → API keys (https://app.callanalyticsapi.com/company/api-keys), create a key with the calls:write scope, and copy it (the full key is shown once). See Authentication.

Path 1 — GHL Workflow → Webhook action (recommended)

This is the no-code path. A workflow watches for a completed call and POSTs it to our inbound endpoint.

1. In GHL, go to Automation → Workflows and create or open a workflow.
2. Add a trigger such as Call Completed (or Customer Replied / whatever fires when the recording exists).
3. Add a Webhook action.
4. Set Method to POST and the URL to:

   https://api.callanalyticsapi.com/webhooks/inbound/generic

5. Under Headers, add:

   X-Api-Key: cc_3a91f8e2_your_api_key
   Content-Type: application/json

6. Set the Body to JSON and map GHL custom values into the fields our endpoint accepts.

JSON body to configure

Use GHL's {{ }} merge fields. Our inbound endpoint accepts flexible field names, so GHL's native naming maps cleanly:

{
  "external_call_id": "{{contact.id}}-{{message.id}}",
  "contact_name": "{{contact.name}}",
  "phone": "{{contact.phone}}",
  "email": "{{contact.email}}",
  "recording_url": "{{message.recording_url}}",
  "duration": "{{message.duration}}",
  "agent_name": "{{user.name}}",
  "agent_email": "{{user.email}}",
  "contact_id": "{{contact.id}}",
  "source_system": "gohighlevel"
}

What you get back

A 201 with {"call_id":…,"status":"received"}. Resubmitting the same external_call_id returns 200 "duplicate" instead of creating another call, so workflow retries are safe.

Path 2 — REST API directly

If you trigger from your own backend (e.g. a GHL marketplace app or a middleware service), call the REST API instead. This gives you the full parameter set and structured responses.

curl -X POST https://api.callanalyticsapi.com/v1/calls \
  -H "Authorization: Bearer cc_3a91f8e2_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "external_call_id": "ghl-ct_993-msg_77",
    "customer_name": "Acme Corp",
    "customer_phone": "+15125550199",
    "recording_url": "https://storage.example.com/rec/77.mp3",
    "rep_name": "Jordan Lee",
    "crm_contact_id": "ct_993",
    "source_system": "gohighlevel"
  }'

See Calls for the full reference, and uploads if you have the audio file rather than a URL.

Receiving the report back in GHL

To get the finished analysis back into GHL, use an outbound webhook into a GHL Inbound Webhook trigger:

1. In GHL, create a workflow with an Inbound Webhook trigger and copy its URL.
2. In our app, go to Company → Webhooks, add an endpoint with that GHL URL, and subscribe it to call.report_completed (and optionally call.compliance_alert_detected, call.buying_signal_detected).
3. When a report is ready, we POST it to GHL. In the GHL workflow, map the report fields (report.overall_score, report.summary, report.crm_note) into contact custom fields, notes, or notifications.
4. Verify the X-Cadence-Signature header if you proxy through your own service. See Webhooks for the signing format.

Because the payload includes crm_contact_id (the {{contact.id}} you sent in), you can match the report back to the exact GHL contact.