Native GoHighLevel tools are failing with: “GoHighLevelMCPCredential or its authenticationSession not found”. We are not using MCP tools. Only using: gohighlevel.calendar.availability.check gohighlevel.calendar.event.create get_contact / create_contact GoHighLevel integration is connected (green check). GoHighLevel MCP is not connected. This looks like provider routing incorrectly requiring MCP credential for native tools. Please check tool provider mapping for this workspace and rebind native tools to non-MCP credential path. https://cdn.discordapp.com/attachments/1451261180437073951/1451261180906573910/Screenshot_2025-12-18_211135.png?ex=697ce6cc&is=697b954c&hm=ebf3ca669c03ddd7d4b9a48bfec4cbba3849c58a4d3ffd830d4d74e0190a365f&

Action Required: To resolve the "GoHighLevelMCPCredential or its authenticationSession not found" error for native GoHighLevel tools, go to the Vapi Dashboard and ensure your native GoHighLevel integration is selected as the provider for each tool: 1. Navigate to Dashboard > Assistants > [Your Assistant] > Tools. 2. For each GoHighLevel tool, confirm the provider is set to your standard GoHighLevel credential (not MCP). 3. Click Publish to save changes. *If the issue persists, disconnect and reconnect your GoHighLevel integration under Providers Keys > Tools Provider > GoHighLevel to refresh the credential mapping.* For more details, see the [GoHighLevel integration guide](https://docs.vapi.ai/tools/go-high-level). Source: - [GoHighLevel Integration](https://docs.vapi.ai/tools/go-high-level)

Hi M.Khatib, Thanks — I checked the docs and related tickets. Next steps I will take now on your workspace: 1. Verify each GoHighLevel tool’s provider mapping in Dashboard > Assistants > \[Your Assistant\] > Tools and ensure they point to the standard GoHighLevel credential (not an MCP credential). (See guide: https://docs.vapi.ai/tools/go-high-level) 2. If any tool is bound to MCP, rebind it to the standard GoHighLevel credential and Publish. 3. If mappings look correct but error persists, I will disconnect and reconnect the GoHighLevel integration under Providers Keys > Tools Provider > GoHighLevel to refresh credential mapping. Please confirm the assistant ID and org ID for the workspace you want me to check, and I’ll inspect and fix the tool-provider bindings.

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.

Hi, Our engineering team has confirmed that the fix for the GoHighLevel integration issue is already in progress, with an estimated release timeframe of Q1 2026. We’ll update you as soon as the patch is live. Thank you for your patience. Best, Vapi Support