GoHighLevel connection expired or revoked

Last updated: July 17, 2026

What you'll see

On Settings > CRM, the GoHighLevel card shows Needs attention with GoHighLevel connection expired.

CRM conversation history, payments, client matching, and calendar sync stay paused until you reconnect with a valid GoHighLevel API key and Location ID.

Why this happens

GoHighLevel rejected the API key Call-E saved for your organization. Common causes:

  • The API key or private integration token expired.
  • Someone revoked or rotated the key in GoHighLevel.
  • The Location ID no longer matches the subaccount tied to that key.

This is a GoHighLevel account change on your side — Call-E support cannot refresh the key for you.

How to fix it

  1. In GoHighLevel, open your subaccount settings and confirm the API key or private integration token is still active. Copy the current API key and Location ID.
  2. In Call-E, open Settings > CRM.
  3. On the GoHighLevel card, click Disconnect.
  4. Click Connect on the GoHighLevel tile.
  5. Enter the current API key and Location ID, then click Save.

After Call-E verifies the credentials, the status badge should return to Healthy. Click Sync Now if you want to pull recent CRM data immediately.

If you use a personal subaccount for calendar sync

If your Calendar card uses a personal GoHighLevel subaccount, update that connection too:

  1. On the Calendar card, click Update subaccount (or Connect personal subaccount if you have not set one up yet).
  2. Enter the current API key and Location ID for your personal subaccount.

If it still fails

  • Confirm the API key includes the read scopes listed in Connecting Call-E to GoHighLevel.
  • Confirm the Location ID matches the subaccount you intend to connect.
  • If your GoHighLevel account uses a branded app domain, enter it in GoHighLevel app domain on the provider card.

Related