HighLevel Integration Guide

What You Need

• A HighLevel Private Integration Token (PIT).
• The HighLevel location ID where contacts will be created or updated.
• Required PIT scopes for cleanLeads CRM sync.

Required Token Scopes

At minimum, your PIT must include these scopes for cleanLeads to work:

• contacts.write - required for contact upserts.
• locations/customFields.readonly - required to sync custom fields from your location.

Optional but recommended if you also use broader HighLevel workflows:

• contacts.readonly
• locations/customFields.write
• locations/tags.readonly and locations/tags.write
• opportunities.readonly and opportunities.write

Connect HighLevel in cleanLeads

1. Open Settings - Integrations.
2. Paste your HighLevel PIT and location ID.
3. Click Save and Connect to validate the credentials.
4. Click Sync custom fields to pull your HighLevel contact custom field schema.

How Custom Field Sync Works

cleanLeads reads custom fields directly from your HighLevel location and stores the mapping context during export. This lets us push standard contact data plus matching custom field values into HighLevel in one flow.

If sync fails, verify PIT scopes, location ID, and that the token is still active.

Lead Requirements

To send a contact through the HighLevel upsert API, the lead must include at least one of:

• Email address
• Phone number

Leads without both values are rejected before the request is sent.