--- title: "GoHighLevel - Auto-Respond Docs" description: "Push every Auto-Respond lead into GoHighLevel as a contact, with tags, notes, and phone-based deduplication." source: https://auto-respond.com/docs/integrations/gohighlevel/ last_updated: 2026-10-16 --- ![GoHighLevel documentation guide](https://auto-respond.com/assets/docs/integrations-gohighlevel.svg "GoHighLevel Documentation") A visual guide to the GoHighLevel documentation, covering the setup, configuration, and workflow details explained on this page. Documentation illustration for GoHighLevel. # 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](https://auto-respond.com/docs/integrations/ghl-messenger/). ## What gets synced Every lead pushed into GoHighLevel includes: - First name - Last name - Phone number - Email - 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 lead in CRM only when contact info is received Label: **Create lead in CRM only when contact info is received**. Default: off. - **When on** - GoHighLevel gets the lead only once the lead has shared a phone number or email, and only if **CRMs** is checked under **Trigger integrations:** in the source’s [Contact Info](https://auto-respond.com/docs/messaging-settings/contact-info/) tab for that kind of contact info. - **When off** - GoHighLevel gets the lead as soon as the lead first reaches out, even before you have their contact info. ### Create only new leads Label: **Create only new leads**. Default: off. - **When on** - If your business had already messaged the lead before Auto-Respond first received the conversation, the lead’s contact info is not sent to GoHighLevel. New messages in a conversation don’t send the lead again either. - **When off** - Those leads and messages are sent too. 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. - Needs **AI Assistant** with **Short** or **Long** conversation in Conversation Setup. - Can’t be turned on together with **Create lead in CRM only when contact info is received** or **Create only new leads**. ### Custom tags On **LeadConnector (Recommended)** only. - **With tags added** - Those tags go on the contacts this source sends to GoHighLevel. - **With none added** - The contact is tagged with the source’s name. ### 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. ## How do I automatically tag LeadConnector contacts based on their lead source? Add a custom tag on each lead source’s LeadConnector card. Tags are set per source, so a `yelp` tag on the Yelp source’s card goes on the contacts that source sends to GoHighLevel. With no custom tags set, Auto-Respond tags the contact with the source’s name. ### Open the source’s LeadConnector card Open the source → **Messaging Settings** → **Integrations** tab → **CRM** sub-tab → **LeadConnector (Recommended)**. ### Give the source its own settings If **Inherit from parent** is on, turn it off (the tags field is locked while the source inherits), and make sure **Enable** is on. ### Add the tag, then repeat on each source In **Custom tags**, type the tag and press Enter; it saves at once. Repeat on each other source with its own tag. Custom tags replace the default source-name tag, and [LeadConnector Messaging Sync](https://auto-respond.com/docs/integrations/ghl-messenger/) on the same source shares the tag list. To keep the source in a field instead, map **Source** to a LeadConnector custom field under **Custom field mappings**; the value is the source type, such as `YELP`. 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](https://help.gohighlevel.com/support/solutions/articles/155000002482-workflow-trigger-contact-tag), checked October 2026). ## 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 lead in CRM only when contact info is received** 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](https://auto-respond.com/docs/integrations/ghl-messenger/). *** Questions about the GoHighLevel integration? Email . Last updated: October 16, 2026