Skip to main content
You connect HighLevel once at the MSP level, with a Private Integration token made in the sub-account that holds your leads, and that sub-account’s Location ID. This works for GoHighLevel, LeadConnector and every white-label brand of HighLevel.

​
1. Create a Private Integration token in HighLevel

1

Open Private Integrations

Sign in to the sub-account that holds your leads and open Settings, then Private Integrations. Click Create new Integration and name it “Neo”.Make the token in the sub-account, not in the agency view: an agency token cannot read a sub-account’s contacts. If you do not see Private Integrations, ask your HighLevel agency (the company you buy HighLevel from) to turn it on for your sub-account, or turn it on under Labs.
2

Choose the scopes

Add what your agents need. Always add locations.readonly, which Neo checks the token with, and businesses.readonly, which maps your businesses to your PSA companies. To copy hot leads into your PSA, add:
  • contacts.readonly and contacts.write
  • businesses.readonly
  • locations/customFields.readonly
  • users.readonly
Add more when agents work other areas, such as opportunities.readonly and opportunities.write. Neo also checks the permission groups you set per agent, so a scope alone never lets an agent change something.
3

Copy the token

Click Create, then copy the token. HighLevel shows it once.
4

Copy the Location ID

In the same sub-account, open Settings, then Business Profile, and copy the Location ID. It is also the part of the sub-account’s address after /location/.
If you rotate the token later, save the new one in Neo before the old one expires.

​
2. Add the token in Neo

1

Open Integrations

Open Integrations → HighLevel in the Neo Dashboard. The card is under Sales & Quoting.
2

Save the token

Paste the token in Private Integration Token and the ID in Location ID, and click Save. Neo reads your sub-account with them before it saves, so a wrong token or ID is rejected straight away.
3

Check the company mapping

After the next sync, open the Organization Mapping tab and confirm the matches between your HighLevel businesses and your PSA companies.

​
3. Turn HighLevel on per agent

Open the agent from Agents, go to its Tools & Settings tab, click Marketplace, and expand the HighLevel block. Pick a preset, then change any group.

​
Copy hot leads into your PSA

In HighLevel, create two contact custom fields if you do not have them yet:
  • the field your team sets when a lead becomes hot, such as a dropdown “Lead status” with the option “Hot”;
  • a single-line text field, such as “Synced to PSA”, that only Neo writes.
Set up a scheduled agent, for example every 15 minutes. Set the HighLevel group Contacts to Read / Write, and Businesses and Custom Fields, Tags & Schemas to Read Only. Give it your PSA’s companies and contacts groups at Read / Write (Autotask Companies and Contacts), and on Autotask Admin at Read Only, where Neo reads the fields a new company needs and your company types. Say in its instructions:
  • the ready field and its value, and the synced field, by their names in HighLevel;
  • the company type a new PSA company gets (Neo uses “Prospect” when you name none, else “Lead”);
  • who owns a new company in your PSA. Without one, Neo uses the PSA technician whose email matches the HighLevel user the lead is assigned to, and skips a lead it cannot match.
Each run finds the leads with the ready value and an empty synced field. For each one, Neo looks for the contact in your PSA by email first, so a lead you already have is only marked. Otherwise it finds the PSA company (through a confirmed business match, or one PSA company with that exact name), creates the company when there is none, creates the contact, and then writes the PSA company and contact ids into the synced field. Neo never changes or deletes an existing PSA record. A lead it cannot place, such as one whose company name matches two PSA companies, stays unmarked and is listed in the agent’s report. To copy a lead again, clear its synced field.

​
Changes that always ask a technician

See Safety Controls in HighLevel API.