I have followed the https://docs.vapi.ai/tools/go-high-level, tried both mcp and api without luck. I can't seem to get any of the tools to work. MCP doesn't show green on the integrations list, API does. Today is {{"now" | date: "%A, %B %d, %Y, %I:%M %p", "America/Chicago"}} is entered in the system prompt. Any ideas on how to get this to work?

Thank you for the details. To help narrow down the issue, could you let me know if you see any specific error messages or failed steps when trying to use the GoHighLevel tools (for example, during tool creation, connection, or when making a call)? This will help identify where the process is breaking. Sources: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level) - [GoHighLevel Tools Setup Guide](https://docs.vapi.ai/tools/GHL)

The assistant says it cant access the scheduler due to an error

Maybe you should try using make.com or n8n

Hi Chow, Thanks — steps to try next: 1. Verify contact flow: ensure your assistant calls Get Contact (or Create Contact) and receives a valid contactId before Create Event. Docs: https://docs.vapi.ai/tools/go-high-level 2. Test each tool call in logs: open Dashboard → Observe → Call Logs, find a failed call and share the call ID. That shows the tool response (403, empty availability, etc.). 3. For MCP vs API: if MCP doesn’t show green, switch to a location-level API key (private token) in GHL, reconnect in Dashboard → Provider Keys → GoHighLevel, then re-create/update the tools. Many users get reliable results with the API token when MCP is flaky. 4. Check Check Availability tool metadata: confirm the correct calendarId, timezone, and that startDate/endDate are sent as epoch ms. If your system prompt uses dynamic dates, ensure timezone matches the tool metadata. 5. If availability returns empty while GHL shows free slots, try creating a test event manually in GHL with the same calendarId to confirm permissions, then retry the tool. 6. Share one failing call ID and which connection method (MCP or API) produced it — I’ll inspect the tool responses in the logs and advise the exact fix.