Skip to main content

​
LeadConnector (GoHighLevel)

With the LeadConnector integration, the contacts your ChatNorris agent confirms reach your LeadConnector / GoHighLevel sub-account on their own. When the visitor confirms their email or phone, depending on what you turn on, the agent:
  • creates the contact in your sub-account or updates the one that already exists;
  • adds a tag to it, useful for triggering your workflows in LeadConnector;
  • adds a note to it with the link to the conversation in ChatNorris.
ChatNorris never reads or changes anything else in your LeadConnector account.

​
Requirements

  • A ChatNorris account on the Standard or Premium plan. You can see the plans at chatnorris.ai/pricing.
  • At least one agent created in ChatNorris. If you don’t have one yet, follow Create an agent.
  • Access to the LeadConnector / GoHighLevel sub-account where you want to receive the contacts, with permission to create a Private Integration.
  • The Owner or Admin role in your ChatNorris organization.

​
Connect LeadConnector

Each agent connects to one sub-account. You need two pieces of information: a Private Integration token and the sub-account’s Location ID.
1

Create the token in the sub-account

Go into the sub-account (not the agency) and open Settings → Private Integrations → Create new Integration. If you don’t see Private Integrations in Settings, turn it on first in Settings → Labs.
2

Check the permissions and copy the token

Give it a name (for example “ChatNorris”) and check the contacts.readonly and contacts.write permissions. Create the integration and copy the token: it’s shown only once.
3

Copy the Location ID

It’s in Settings → Business Profile. It also appears in the sub-account’s URL, after /location/.
4

Open the agent's Integrations hub

In ChatNorris, go to My agents → [your agent] → Integrations and choose LeadConnector.
5

Paste both values and connect

Paste the token in Private Integration token (it starts with pit-) and the identifier in Location ID, and click Connect. With Test connection you confirm that they work before you use them in the Action.
The hub only shows the token’s last 4 characters. If you rotate it in LeadConnector, use Replace key in the row’s ··· menu: the connection stays the same and the Action is not affected.

​
Configure the Action

Connecting the sub-account doesn’t send anything yet. To choose what the agent does in LeadConnector:
1

Create the LeadConnector Action

Go to My agents → [your agent] → Actions, click New action, and choose LeadConnector.
2

Choose the capabilities

Turn on the ones you want (see the table below). Add tag and Conversation note require Sync contact to be on.
3

Turn on the Action and save

With Action enabled on, click Save. From then on, this agent’s confirmed contacts reach your sub-account.
Deleting the Action doesn’t remove the connection from the hub: the sub-account stays connected in Integrations.

​
Disconnect

In My agents → [your agent] → Integrations → LeadConnector, click Disconnect (it’s also in the row’s ··· menu). Contact sync is disabled: the LeadConnector Action is turned off, but it isn’t deleted and keeps its configuration. The token is deleted from ChatNorris. To send contacts again, connect the sub-account again and reactivate the Action. If you only want to stop it for a while, turn off the integration’s Active switch: the token is kept and the Action doesn’t call LeadConnector until you reactivate it.

​
Frequently asked questions

Turn it on first in the sub-account’s Settings → Labs. Remember to create the token inside the sub-account, not in the agency.
No. LeadConnector shows the token only once. Create a new one in Settings → Private Integrations and paste it with Replace key.
LeadConnector looks for duplicates according to your sub-account’s settings. If it finds the contact, it updates it: name and company are only filled in if they’re empty, and the tag is added to the ones it already has.
No. Connecting and testing the integration has no cost in credits. See AI models and credits.
No. Each provider supports only one connection per agent. If you need different sub-accounts, use separate agents.