GoHighLevel

The GoHighLevel integration creates and updates contacts in your GoHighLevel account automatically. In NZ Leads it’s called LeadConnector. The connection is OAuth-based - you click Connect with LeadConnector V2, approve on GoHighLevel, and choose the location to connect, so you don’t need an API key.

ℹ️

You set LeadConnector up once and then choose where it’s used: which businesses, sources, and voice agents send leads to it. Add it from Settings → Integrations in the menu, or from a source’s Messaging Settings → Integrations tab. In the Add integration list it’s LeadConnector, under CRM and field service. Searching HighLevel finds it too.

V2 and V1 connections

Before it is connected, the LeadConnector card asks you to Choose your connection method:

An integration that still uses V1 shows V1 Connection Active on the card. Custom tags and Custom field mappings are available only on V2. To move an integration to V2, click Disconnect LeadConnector, confirm with Yes, then choose V2 - OAuth 2.0 and click Connect with LeadConnector V2. V1 and V2 count as one kind of integration, so a place uses one or the other.

💡

If you’re setting up LeadConnector for the first time, choose V2 - OAuth 2.0.

Not the same as LeadConnector Messaging Sync

There is also a separate LeadConnector Messaging Sync integration (formerly called “GoHighLevel Messenger”) in the same Add integration list. It handles inbound and outbound messaging through GoHighLevel’s Conversations inbox. That is a different integration and is not covered on this page - this page is about syncing leads into GoHighLevel as contacts. See LeadConnector Messaging Sync.

What gets synced

A contact is created once the lead has a phone number or an email address (for Yelp leads, the temporary email address Yelp gives counts too). Every lead pushed into GoHighLevel includes:

When a voice agent’s call report goes to this integration, the contact also gets a note that starts with Call Finished, with the phone number, the call summary, and the recording link.

Connecting GoHighLevel

Add LeadConnector

In NZ Leads, go to Settings → Integrations → Add integration → LeadConnector. The LeadConnector window opens.

You can also start from a source: open the source → Messaging Settings → Integrations tab → Add integration → Create new → LeadConnector. If the tab shows Business Settings Active, switch on Customize for Location first. To reuse a LeadConnector integration your account already has, pick it on the Use existing tab instead.

Click Connect with LeadConnector V2

Under Settings in the window, keep V2 - OAuth 2.0 selected and click Connect with LeadConnector V2. You’ll be redirected to GoHighLevel to authorize the connection.

Approve access in LeadConnector

On LeadConnector’s page, sign in if needed, choose the location to connect, and approve access.

Continue back to NZ Leads

You land on a page that says GoHighLevel connected & active. Click Continue. The Integrations page opens with your LeadConnector integration, and Enabled is already on.

Choose where it’s used

Under Where it’s used, tick the businesses, source types, sources, and voice agents that should send leads to LeadConnector. Ticking a business covers all its sources, including sources added later. If you added LeadConnector from a source’s tab, that source is already ticked, unless it uses another LeadConnector integration.

A place sends to one LeadConnector integration at a time. If you turn this one on where another LeadConnector integration is used, NZ Leads asks you to confirm the replacement.

Options

Enabled

Turns this LeadConnector integration on or off everywhere it’s used. It turns on when you connect with V2. To stop sending for one source only, switch LeadConnector off on that source’s Integrations tab instead.

Create lead in CRM only when contact info is received

Label: Create lead in CRM only when contact info is received. Default: off. You can change it only while Enabled is on.

Create only new leads

Label: Create only new leads. Default: off. You can change it only while Enabled is on.

This option looks at the conversation, not at GoHighLevel: it doesn’t search GoHighLevel for an existing record.

Notify this integration only after the AI determines the lead is interested

Label: Notify this integration only after the AI determines the lead is interested. Default: off. Turning it on asks you to confirm: Let AI decide which leads are sent? → Enable.

Custom tags

Shown once you connect with V2.

If the same source also uses a LeadConnector Messaging Sync integration, the contact gets that integration’s custom tags too.

Custom field mappings

V2 connections only. Fills LeadConnector custom fields on the contact with details from the lead.

  1. Under NZLeads field, choose one of: Lead status, Display name, Project details, Job names, Availability, City, or Postal code.
  2. Under LeadConnector custom field, type the field’s key, for example contact.contact_status. A key copied from LeadConnector with its curly braces works too.
  3. Click Add. Remove a mapping with its delete button.

The mapped values are written each time the contact syncs. A lead field that is empty is skipped, so it never blanks the custom field. There is no lead source field in this list; use Custom tags to mark where a contact came from.

Validate Connection

Tests the OAuth token against GoHighLevel. If the token has been revoked on GoHighLevel’s side, the error is shown here and you’ll need to reconnect.

Disconnect LeadConnector

Removes the OAuth connection. It asks “Are you sure you want to disconnect LeadConnector V2?” - click Yes. This removes the sign-in and the card’s settings, including its options and custom tags. The integration stays where it’s used but sends nothing until you connect it again. To remove the integration itself, click Delete integration in the window.

How do I automatically tag LeadConnector contacts based on their lead source?

Leave Custom tags empty. Each contact is then tagged with the name of the NZ Leads source the lead came from, so every source’s contacts carry that source’s name.

Custom tags replace the default source-name tag on every place that uses the integration, and LeadConnector Messaging Sync on the same source shares the tag list. To give each source its own custom tag, such as yelp, each source needs its own LeadConnector integration with that tag.

In GoHighLevel, a workflow with the Contact Tag trigger runs when a tag is added to or removed from a contact, so the tag can start your follow-up (HighLevel help: Contact Tag trigger, checked October 2026).

Matching and deduplication

NZ Leads remembers the LeadConnector contact it created for a lead and updates that contact as the conversation goes on, instead of creating another one.

New contacts are sent to LeadConnector as “create or update”, so your location’s duplicate-contact settings decide whether an existing contact with the same phone number or email is updated instead.

When NZ Leads updates the contact it created for a lead, it doesn’t replace a real email on that contact with a temporary one, such as the masked address Yelp gives before the customer shares contact info.

A note on appointment booking

LeadConnector can also be the calendar the AI books appointments in, both in text conversations and on voice-agent calls. That’s a separate setting with its own API key, calendar ID, and location ID, not the sign-in above: choose LeadConnector under Appointment Scheduling in a source’s Conversation Setup, or in a voice agent’s Appointments section (see Voice Agent Scheduling Integrations). This page covers only the contacts created from leads.

Turning LeadConnector off

Contacts already in GoHighLevel stay there. You should also revoke the connection on the GoHighLevel side from your GoHighLevel settings if you want it fully removed there too.

Troubleshooting


Questions about the GoHighLevel integration? Email support@nzleads.com.

Get Started