HighLevel

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: 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.

1. 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. 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. 3

   Add the data source

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

4. 4

   Enter your credentials and connect

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

5. 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.

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.

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.

Consent mapping

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.