LeadConnector Messaging Sync (GoHighLevel)
The LeadConnector Messaging Sync integration (formerly named “GoHighLevel Messenger”) sends the conversation itself into GoHighLevel’s Conversations inbox. Inbound lead messages appear in GHL as new conversations, and replies you send from inside GHL are delivered back to the lead. Use this when your team already handles customer replies from inside GoHighLevel and you want Auto-Respond conversations to show up alongside everything else.
In Auto-Respond this integration’s card is labeled LeadConnector Messaging Sync — the product was renamed. If you’re looking for “GoHighLevel Messenger” and don’t see it, that’s the same card.
The LeadConnector Messaging Sync card is on any source’s Messaging Settings → Integrations tab → Messengers sub-tab.
Not the same as the LeadConnector CRM integration
Auto-Respond has two separate GoHighLevel integrations, and both are labeled with the new “LeadConnector” brand name in the UI:
- LeadConnector (CRM) — on the CRM sub-tab. Creates and updates contacts in GHL. Good if you use GHL as your system of record but reply to leads somewhere else.
- LeadConnector Messaging Sync (this page) — on the Messengers sub-tab. Pushes the conversation into GHL’s Conversations inbox so your team replies from inside GHL.
You can use one, the other, or both. They each have their own OAuth connection.
What you’ll get
- Every new lead creates a new conversation in your GoHighLevel Conversations inbox.
- Inbound messages from the lead land in that conversation.
- Replies your team sends from inside GHL Conversations are delivered back to the lead.
- The conversation history lives in GHL, not in Auto-Respond, so your inbox workflow doesn’t change.
Connecting GoHighLevel Messenger
Open the integration
In Auto-Respond, open the source → Messaging Settings → Integrations tab → Messengers sub-tab → LeadConnector Messaging Sync card.
Click Connect
You’ll be redirected to GoHighLevel to authorize the connection. Sign in if needed and approve access.
Choose Company or Location scope
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 the messenger connection to work across multiple sub-accounts under one OAuth connection.
- Choose Location if this Auto-Respond source should only route conversations 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.
Validate and save
Click Validate Connection. If the OAuth token is healthy, you’ll see a green confirmation.
Turn on the Enable toggle
Nothing is pushed to GHL Conversations 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 LeadConnector Messaging Sync connection. When off, it has its own.
Create customer only when contact info is captured
Default: off.
- When on — The GHL conversation is only created once the lead has shared a phone number or email.
- When off — The GHL conversation is created as soon as the lead reaches out.
Create only for new leads
Default: off.
- When on — Returning leads don’t open a fresh conversation in GHL.
- When off — Every lead opens a conversation in GHL (or updates an existing one when the lead is matched).
Include source name
Default: off. When on, the source name is included on the conversation in GHL so your team can see where the lead came from without leaving GHL.
Validate Connection
Tests the OAuth token against GoHighLevel. If the token was revoked on GHL’s side, the error shows here and you’ll need to reconnect.
Disconnect
Removes the OAuth connection. Confirmation required. You should also revoke the connection on the GoHighLevel side from your GoHighLevel settings if you want it fully removed there too.
What the conversation contains
Each conversation in GHL includes:
- The lead’s name (if shared)
- Phone number and email (if shared)
- The original inquiry as the first inbound message
- All follow-up messages from the lead, as they come in
- Replies your team sends back through GHL Conversations
Who handles replies?
When this integration is enabled, you’re telling Auto-Respond that replies will be handled from inside GoHighLevel. Configure your own reply workflow inside GHL (team members, routing rules, automations) — that’s where the conversation lives now.
Disconnecting
Open the LeadConnector Messaging Sync card → click Disconnect → confirm. The OAuth connection is removed from Auto-Respond. Existing conversations in GHL are not deleted; they just stop receiving new inbound messages from this source.
Troubleshooting
- “Validation failed” / token expired — Click Connect again and re-authorize. OAuth tokens can be revoked on GHL’s side at any time.
- Conversations not appearing in GHL — Confirm Enable is on. Check whether the connection was made at Company or Location level; at Company level, make sure Auto-Respond is writing into the location you expect.
- Replies from GHL aren’t reaching the lead — Confirm the connection is still healthy (use Validate Connection). If the token was revoked, reconnect.
- I wanted the CRM sync, not the messenger — Use the separate LeadConnector (CRM) integration on the CRM sub-tab.
Questions about the GoHighLevel Messenger integration? Email support@auto-respond.com.