GoHighLevel Integration Not Working? Here's What to Check

Written by Niyamul Islam Sajal, COO & GHL Certified AdminNovember 17, 20263 min readGoHighLevel

A GoHighLevel integration not working almost always comes down to one of three things: a token that expired, an app hiding under a different name, or a scope nobody granted at setup. None of those fail loudly.

Zaps just stop firing. Contacts stop syncing. Nobody notices until a lead goes unanswered for a week.

HighLevel rebuilt its integrations page around exactly this problem, splitting failures into "connection-level errors," tied to one linked account, and "integration-level errors," which affect the whole app. A connection error usually just needs a reconnect. An integration-level error points at something broken in the app's permissions.

What Usually Causes a GoHighLevel Integration Not Working

Start with authentication. OAuth access tokens expire daily and need refreshing to keep working. When that refresh quietly fails, the fix is simple: disconnect the integration and reconnect it.

Private Integration Tokens behave differently, and that's what catches people out. They're static.

HighLevel's own developer documentation is specific here: a Private Integration Token does not automatically refresh unless you rotate it from the UI. A token wired into a Zapier webhook keeps working until someone rotates or revokes it, then stops with no warning.

Scopes cause a quieter version. A token only reaches the endpoints it was granted at creation. That's often the real story behind a GoHighLevel workflow not triggering: the integration looks fully connected, but the one action that needed a scope nobody added just fails, every time.

The API v1 Cutoff Broke Older Zapier and Custom Connections

If an integration that ran fine for years suddenly died with no changes on your end, check when it was built. API v1 reached end-of-support on December 31, 2025. Existing v1 connections may still respond, but they get no fixes, and HighLevel stopped letting anyone generate new legacy keys.

The replacement is the Private Integration Token, built on API v2. It's more secure by design: each token carries only the scopes you grant it, not the all-or-nothing access an old key had.

Migrating means listing every tool on a v1 key, building one Private Integration per tool, and switching the old key off once it's tested. Agencies handle this as part of ordinary GHL setup and configuration, not a special project.

HighLevel recommends rotating every token roughly every 90 days, even when nothing looks broken. Rotation opens a seven-day window where both tokens work, so nothing just stops mid-update.

Searching for GoHighLevel Inside Zapier? Look for LeadConnector

A different kind of "not working" shows up before a single Zap runs: typing "GoHighLevel" into Zapier's app search and getting nothing back. That's not a bug. Zapier lists the integration under a different name, so a search for the product people actually use turns up empty.

One Zapier user ran into exactly this and posted about it on Zapier's own community forum, asking why GoHighLevel "doesn't seem to exist" on the platform. The answer: the app is called LeadConnector.

Once you find it, LeadConnector's Zapier app covers less ground than most people expect. It offers:

  • One trigger: a pipeline stage change on an opportunity
  • Adding or updating a contact
  • Adding or updating an opportunity
  • Adding a lead to an existing workflow
  • Stopping all workflows for a lead
  • Adding a task

Anything outside that list needs a webhook or a direct API call, which is usually where a custom automation build comes in rather than a plug-and-play Zap.

Contacts landing twice is a separate complaint worth checking against GoHighLevel's duplicate message behavior before assuming the integration is broken.

Reconnect the account, rotate the token, confirm the scope, or search for the right app name, and most "integration not working" tickets close in minutes. The ones that don't are almost always scope problems that surface once a new automation goes live, which is why agencies running white-label support for client accounts check scopes before a launch, not after.

Cover photo by Bikram Bezbaruah on Pexels

Sources (5)

Need help implementing this in GoHighLevel?

Our team builds, automates, and scales GoHighLevel systems for agencies every day. Book a free call and we'll map out exactly what to ship next.

Book a free call