# HighLevel

Connect a HighLevel (GoHighLevel) CRM as a data source: the API key and location it needs, the contacts, events and deals it syncs, how its fields map to Instasent attributes, and how to map its marketing status to consent.

**Language:** en
**Audience:** platform
**TLDR:** HighLevel (GoHighLevel) is a native connector that syncs your CRM contacts and deals into Instasent on a one-way periodic sync. You connect it with an API key you create in HighLevel (Settings → Private Integrations → API) and paste into Instasent along with the Business Location ID of the sub-account you want to sync.
**Translation key:** platform.data-sources.connectors.highlevel
**Search keywords:** HighLevel, GoHighLevel, GHL, CRM, API key, private integration, location ID, contacts, deals, events, connect HighLevel, HighLevel integration, HighLevel consent
**Related pages:** /platform/es/data-sources/connectors/highlevel, /platform/en/data-sources/connectors, /platform/en/data-sources/connectors/activecampaign, /platform/en/data-sources/managing, /platform/en/consent
**Docs index (every page):** https://docs.instasent.com/llms.txt
**This zone's index:** https://docs.instasent.com/platform/en/llms.txt
**This page:** https://docs.instasent.com/platform/en/data-sources/connectors/highlevel/ (HTML) · https://docs.instasent.com/platform/en/data-sources/connectors/highlevel.md (Markdown)
**Other language (es):** https://docs.instasent.com/platform/es/data-sources/connectors/highlevel.md

HighLevel (GoHighLevel) is the native connector for the HighLevel CRM. Once connected,
it syncs your contacts and deals into Instasent so your audience and your CRM activity
stay current.

## How to connect

HighLevel connects with an **[API key](/platform/en/data-sources/connectors#api-key)**:
you create the key in HighLevel first and paste it into Instasent, along with the
location it applies to. You provide two values — an **API Key** and a **Business
Location ID**.

> **Warning**: Create the API key in HighLevel **before** connecting. The panel won't let you
> continue without valid credentials.

#### 1. Create an API key in HighLevel

In HighLevel, go to **Settings → Private Integrations → API** and create a key.
Copy the key it generates.

#### 2. Find your Business Location ID

Your **Business Location ID** identifies the sub-account whose data you want to
sync. You'll find it in your account settings.

#### 3. Add the data source

In **Data sources**, select **Add data source** and choose **HighLevel** from the
Integrations section.

#### 4. Enter your credentials and connect

On the **Connect** step, fill in your **API Key** and **Business Location ID**, then
connect.

#### 5. Initial import

The connector imports your existing contacts, then keeps syncing periodically.

After connecting, the wizard continues through **Mapping**, **Merge** and **Tags**, the
same steps as a CSV import.

![The HighLevel connector page with its description, what it imports, and the contact fields it maps, with Connect HighLevel to start](/platform/en/data-sources/images/highlevel--1-connect.png)
*The HighLevel connector page: what it brings into Instasent and the contact fields it maps, with Connect HighLevel to start.*

## What it syncs

- **Contacts** — your CRM contacts, with name, email and phone.
- **Deals** — CRM deal activity, brought in as events for use in segments and
  automations.

The direction is one-way, **from HighLevel into Instasent**, with a periodic sync that
keeps contacts and deals current. Contacts unify by email and phone — see
[unification](/platform/en/data-sources/managing#how-unification-works).

## Field mapping

HighLevel contact fields map to the matching Instasent attributes (email to `_email`,
phone to `_phone_mobile`, name fields to theirs), and deal activity arrives as events.
Confirm the mapping on setup; see
[field mapping](/platform/en/data-sources/managing#field-mapping).

## Consent mapping

{/* VERIFY: the exact HighLevel → Instasent consent mapping is not yet confirmed. The mapping below applies the consent golden rule; confirm against the connector's actual behaviour before treating it as definitive. */}

Map HighLevel's marketing status to Instasent's marketing-preference attribute
(`_accepts_marketing_*`) following the consent golden rule:

| HighLevel status   | Instasent value | Meaning                     |
| ------------------ | --------------- | --------------------------- |
| Opted in           | `true`          | Accepted marketing          |
| No status recorded | `null`          | No preference               |
| Opted out          | `false`         | Actively declined marketing |

Only an **active opt-out** becomes `false`. A contact with no recorded marketing status
maps to **no preference** (`null`), never to `false`. See
[Consent](/platform/en/consent/marketing-preference-vs-suppression).

---

This is one page of the Instasent documentation. For the complete machine-readable index of every guide and API reference, fetch https://docs.instasent.com/llms.txt — start there for full context.