Can't connect my highlevel account

  • n8n version: Version 2.16.1

  • Database (default: SQLite):

  • n8n EXECUTIONS_PROCESS setting (default: own, main):

  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker, ngrok

  • **Operating system: windows 11

    hi, do anyone know or encounter this problem? I can’t connect my highlevel account. always popping this error. I already have my credentials ready in my highlevel dev account still can’t connect it properly. Any help will do Thanks. For context I am using self hosted n8n in docker and tunnel with ngrok.
    **

hope you are doind well @initialize
I’m not 100% sure it is only the callback URL, this specific error more strongly suggests the HighLevel app/integration ID configured in your credential is invalid, deleted, or does not match the correct HighLevel environment/location. I would first verify the Integration/App exists in your HighLevel developer account, regenerate the client credentials if needed, then recheck the redirect URL with your current ngrok domain.
ps: make sure your current public ngrok HTTPS URL is what n8n is actually using (N8N_HOST/N8N_PROTOCOL/WEBHOOK_URL)

Hi thanks for the replies, I try to check the callback from my n8n self-hosted and it’s 100% fine. I also tried creating in new free trial account directly in n8n cloud and the output is still the same

Did you try return to version 2.15? its more stable.
I suggest deleting and recreating the GoHighLevel OAuth app (or creating a fresh one). You’ll need to re-add the callback URL, generate a new Client ID and Secret, and then reconnect

Hi @Initialize, I hope you’re doing well!

If you’re using the free ngrok plan, your URL will change every time you restart, and this may be causing the error.

See my suggestion below; check if it makes sense for you.

Alternative Solution: Create a Private HighLevel Integration + Use Generic OAuth2 on n8n

Step 1 — Create a Private App in the HighLevel Developer Portal

  1. Go to https://marketplace.gohighlevel.com/My AppsCreate App
  2. Choose Private Integration (not Marketplace)
  3. Under Redirect URLs, add: https://<your-ngrok-subdomain>.ngrok-free.app/rest/oauth2-credential/callback
  4. Copy your Client ID and Client Secret

Note: If you are using the ngrok free plan, your URL will change upon restarting, and this may generate the same error. Consider using ngrok static domains or a self-hosted tunnel alternative. —

Step 2 — Create an OAuth2 credential in n8n

In n8n, go to Credentials → New → OAuth2 API and fill in:

| Field | Value |

|—|—|

| Grant Type | Authorization Code |

| Authorization URL | https://marketplace.gohighlevel.com/oauth/chooselocation |

| Access Token URL | https://services.leadconnectorhq.com/oauth/token |

| Client ID | (from Step 1) |

| Client Secret | (from Step 1) |

| Scope | contacts.readonly contacts.write locations.readonly (add as needed) |

| Authentication URI query parameters | (leave blank) | Click on Connect my account — the HighLevel OAuth screen should open and authentication should be successful.


Step 3 — Use the HTTP Request node instead of the HighLevel node

Since the native HighLevel node does not accept a custom application, use the HTTP Request node with your new OAuth2 credentials to call the HighLevel API directly:

  • Base URL: https://services.leadconnectorhq.com

  • Example: GET /contacts/ with your location ID as the query parameter


I hope this helps! If this solved your problem, mark this answer as the solution and leave a heart.

Stay well. All the best!

@initialize that error No integration found with the id: 69dddaa17cf06af835d557fe means the app got deleted or you’re mixing up Sub-Account vs Agency level apps in GHL. Go to marketplace.gohighlevel.com, check under My Apps if that app ID still exists — if not, create a brand new app, copy the fresh Client ID and Secret into n8n, and make sure you pick the right app type (Private, Agency level)

有幾件事我會先檢查:

  1. 驗證您在 HighLevel 開發者應用中配置的 OAuth 重新導向 URL 是否與您的 ngrok URL 完全相符(包括 https 和任何尾部路徑)。

  2. 確保您的 ngrok 隧道尚未變更,因為免費 ngrok URL 在重新啟動後通常會輪換。

  3. 檢查您的用戶端 ID 和用戶端密鑰是否來自正確的 HighLevel 開發者應用。

  4. 在授權嘗試期間查看 n8n 日誌—通常在通用連線失敗後面隱藏著更具體的錯誤。

如果您可以分享來自彈出式視窗或 n8n 日誌的確切錯誤訊息,將更容易查出問題所在。