Failed to Exchange OAuth Code for Access Token when Connecting a GHL Sub-account

Issue

When attempting to connect a GoHighLevel (LeadConnector) sub-account, users may receive the error:

"Failed to exchange OAuth code for access token."

This can occur even when:

• The agency OAuth connection is healthy.

• Other sub-accounts connect successfully.

• A Hard OAuth Reset has already been performed.

• The correct Assistable domain (https://createassistants.com) is being used.

Root Cause

One possible cause is that the affected GoHighLevel sub-account is paused or suspended on the GHL side.

When a location is paused, GoHighLevel does not issue a valid OAuth token for that location, causing the OAuth exchange to fail.

How to Verify

1. Log into your GoHighLevel Agency account.

2. Locate the affected sub-account/location.

3. Check whether the location is Paused or Inactive.

4. If it is paused, reactivate the location.

5. Retry the LeadConnector connection in Assistable.

Resolution

Once the GHL location is reactivated:

• Reconnect the LeadConnector integration.

• If necessary, use Connect to GHL again from the Assistable dashboard.

• The OAuth connection should complete successfully.

Troubleshooting Checklist

Before escalating, verify:

• ✅ You're using https://createassistants.com

• ✅ The Agency OAuth connection is healthy.

• ✅ The Assistable Marketplace app is installed.

• ✅ The Workspace Admin is performing the connection.

• ✅ The affected GHL location is not paused or suspended.

Outcome

In one reported case, the issue was not with Assistable or OAuth itself. The affected GoHighLevel sub-account had been paused, preventing GHL from issuing a valid OAuth token. After reactivating the location and reconnecting, the integration worked successfully.