GoHighLevel
The GoHighLevel integration creates and updates contacts in your GoHighLevel account automatically. The connection is OAuth-based — you click Connect, approve on GoHighLevel, and at the end you choose whether the connection should be at the company level (for agencies managing many sub-accounts) or at a specific location level.
In Auto-Respond this integration’s card is labeled LeadConnector — the product was renamed. If you’re looking for “GoHighLevel” on the CRM sub-tab and don’t see it, pick the LeadConnector card.
The LeadConnector card is on any source’s Messaging Settings → Integrations tab → CRM sub-tab.
Recommended vs Legacy
Auto-Respond offers two versions of this integration:
- LeadConnector (Recommended) — the current, up-to-date connection. New customers should use this one.
- LeadConnector (Legacy) — the older connection, kept only for existing customers who haven’t migrated.
To avoid conflicts, only one of these is shown on a given source at a time. If you’re setting up GoHighLevel for the first time, you’ll see LeadConnector (Recommended). If you already had the Legacy connection set up, you’ll continue to see Legacy until you migrate.
If you’re a new user, always use LeadConnector (Recommended).
Not the same as LeadConnector Messaging Sync
There is also a separate LeadConnector Messaging Sync integration (formerly called “GoHighLevel Messenger”) on the Messengers sub-tab. 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
Every lead pushed into GoHighLevel includes:
- First name
- Last name
- Phone number
- Postal code
- Tags
- A note with the source and the original inquiry
Connecting GoHighLevel
Open the integration
In Auto-Respond, open the source → Messaging Settings → Integrations tab → CRM sub-tab → LeadConnector (Recommended) card.
Click Connect
You’ll be redirected to GoHighLevel to authorize the connection. Sign in if needed and approve access.
Choose Company or Location
At the end of the OAuth flow, GoHighLevel (and Auto-Respond) will ask whether this connection should be at the Company level or a specific Location.
- Choose Company if you’re an agency and want Auto-Respond to place leads across multiple sub-accounts under one connection.
- Choose Location if this Auto-Respond source should only write into a single GoHighLevel location.
You’re returned to Auto-Respond
After authorizing, you land back on the integration card. The connection is now set.
Turn on the Enable toggle
Nothing is sent to GoHighLevel until Enable is on.
Options
Enable
Turns the integration on or off for this source. Default: off.
Inherit from parent
Only shown on a location with a parent business. When on, the location uses the parent’s GoHighLevel connection and settings. When off, it overrides them.
Create customer only when contact info is captured
Default: off.
- When on — The GoHighLevel contact is only created after the lead shares a phone number or email.
- When off — A contact is created at first contact, even without phone or email.
Create only for new leads
Default: off.
- When on — If a GoHighLevel contact already matches on phone, the integration leaves it alone.
- When off — The existing contact is updated, tags are added, and a new note is appended.
Include source name
Default: off.
- When on — The source name is added to the note (and often as a tag) on the GoHighLevel contact.
- When off — Source isn’t included.
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
Removes the OAuth connection. Confirmation required.
Matching and deduplication
GoHighLevel contacts are matched by phone number. This is how duplicate contacts are avoided even if the name or email differs slightly.
One important detail: if a contact in GoHighLevel already has a real email, Auto-Respond will not overwrite it with a temporary placeholder email (such as the anonymized address Yelp returns before contact info is shared). The real email wins.
Disconnecting
Open the LeadConnector card → click Disconnect → confirm. The OAuth connection is removed from Auto-Respond. You should also revoke the connection on the GoHighLevel side from your GoHighLevel settings if you want it fully removed there too.
Troubleshooting
- “Validation failed” / token expired — Reconnect via OAuth. Click Connect again and re-authorize.
- No contacts appearing — Confirm Enable is on. Check whether the connection was made at Company or Location level; if it’s Company-level, check the location routing in GoHighLevel.
- Duplicate contacts — Matching is by phone. If leads are reaching out without sharing a phone number, you may see new contacts that later “catch up” to the real one. Turning on Create customer only when contact info is captured helps.
- My real email got replaced by a temporary one — This shouldn’t happen. Real emails are preserved over temporary ones. If you see this, contact support.
- I meant to set up the messenger sync, not the CRM sync — That’s a different card named LeadConnector Messaging Sync on the Messengers sub-tab. See LeadConnector Messaging Sync.
Questions about the GoHighLevel integration? Email support@auto-respond.com.