I’ve been trying to connect it for a few days. I followed all the steps and granted every required permission, but after setup completes the dashboard still shows it as not connected.

Thank you for sharing the issue. To help diagnose the problem, could you let me know if you see any specific error messages or alerts on the dashboard when the GoHighLevel integration shows as "not connected"? This detail will help pinpoint whether the issue is with permissions, the connection process, or something else. If possible, a screenshot of the dashboard state would also be helpful. Sources: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/GHL) - [Issue Reporting Guide](https://docs.vapi.ai/issue-reporting)

It doesnt have the checkmark that identifies it as connected and also the tools does not work since they lack permissions which indicates that it is not connected

Hi riksa, Thanks — this is a known symptom we've seen when the OAuth/MCP flow doesn't persist the credential. Quick troubleshooting steps (please try in order and tell me results/screenshots): 1. Revoke and retry - In GoHighLevel: Settings → Authorized Apps (or Integration) → revoke Vapi access. - In Vapi: Dashboard → Providers Keys → Tools Provider → GoHighLevel → click Connect and complete OAuth in an incognito window. 2. Browser console + API logs - While reproducing, open DevTools (F12) → Console. If any error appears, copy it. - In Vapi Dashboard → Observe → API Logs: filter recent attempts for GoHighLevel and paste any error lines or request IDs. 3. Confirm you're using the direct GHL connector (not MCP) - Docs: https://docs.vapi.ai/tools/go-high-level - If you attempted MCP or used a Location API key option earlier, undo that and use the Connect button in Providers Keys as above. 4. Verify sub-account & calendar permissions in GHL - Ensure the sub-account you authorized includes calendar write permissions and the calendarId used in tools matches the sub-account’s calendar (Settings → Calendars shows calendarId). 5. If you see the specific error "GoHighLevelMCPCredential or its authenticationSession not found" or logs show MCP usage: - That indicates the system attempted MCP/old API method. Please confirm you used the Connect flow in Providers Keys (not manual API key) and share the exact console/API log error. What I need from you next: - A screenshot of the Providers Keys → GoHighLevel page showing the missing checkmark. - Any console error text or an API log entry from step 2. If you share those, I’ll escalate with the exact errors and recommended backend fix.

Tried all i am facing the same issue

You know this is a known issue none of those steps you shared will solve. This has been an issue since mid November. Does Vapi even care about fixing the issue? Just be honest with us if it's never going to be fixed so we can start learning a different platform if it's not.

This is definitely quite a lie. You guys are not saying that none of this stuff is working in there, and there is no such thing as a direct connector for GHL because there's nothing to connect with you guys if it's not MCP. So what does the API key even do? Because I'm not even finding anything that the API key is used for in there. The MCP doesn't work and you guys just keep acting like it. It's literally been seven weeks. So totally alpha-vappy, totally out of here. Checking out Retail and all the other ones because this platform is done.

Nothing worked Aniah, and i get no errors except for CORS ones, can you please escalate it as you mentioned and offer a complete solution, thank you.

@User any update on when will the MCP be fixed?

its not fixed

@Vapi are you going to fix this?

Hi, I am sorry for the delayed response. There is an ongoing issue related to GHL integration. And it will be addressed by end of Q1 this year. Thank you for your patience regarding this issue.

Is this fixed yet?

Hi @theromper, we are currently working on this issue. I apologize for any inconvenience this might have caused you.

Is there any update? Getting close? Still done by the end of March?

Hi @theromper, Yes, our team has not reported any delay regarding this issue. So it should be resolved by end of march.

Any closer today? We're 1/3 the way through. This has been affecting my business since December.

Hi