GHL Calendar Native Tools - Free Slots Empty + App...
# support
d
Hi, I'm having two issues with VAPI's built-in GHL calendar tools: Issue 1 - Free slots returning empty The availability check tool returns 'Completed successfully' but gives no slots, so the assistant falls back to sending a booking link. It worked correctly before (see screenshots). GHL calendar has availability set up, Private Integration API key connected with correct scopes. Issue 2 - Appointment not saving to GHL When it did work, 'Create Appointment - Completed successfully' appeared in VAPI logs, but the appointment never showed up in GHL calendar. How do I fix both of these? Happy to provide more details. https://cdn.discordapp.com/attachments/1494137973325692928/1494137973967552553/image.png?ex=69e183ec&is=69e0326c&hm=38ccbf2ec47fdc7ec363041643ab6dd68cfffc3cdbef6d1d03b5d3a79a22af7d& https://cdn.discordapp.com/attachments/1494137973325692928/1494137974491971684/image.png?ex=69e183ec&is=69e0326c&hm=2d6396e169dcf0e5ceb1d4e95440e34ac392cdeb97ede452e4aebf33cb12115c& https://cdn.discordapp.com/attachments/1494137973325692928/1494137975137763519/image.png?ex=69e183ed&is=69e0326d&hm=79bf388d0b2d825723c98f6b92abbd07b6d54c10a821f859747dcb6f9bacfc3e&
a
From what you described, this is usually caused by: • Wrong calendar ID or location mismatch (causes empty slots) • Timezone or availability config mismatch • Missing required fields (like contact ID) when creating the appointment, so it “succeeds” but doesn’t save in GHL I can debug your setup, fix the slot retrieval, and make sure appointments actually get written into GHL properly. @Daniel Lee,
c
Hi, Thank you for reaching out. We’d like to let you know that the GoHighLevel (GHL) MCP integration issue is a known problem, and our team is actively working on a fix. Thank you for your patience
m
This usually points to a sync mismatch between VAPI ↔ GHL (not your setup). When “Get Free Slots” returns empty but succeeds, it’s often pulling from the wrong calendar ID, timezone, or missing user assignment worth double-checking those first. Faster workaround: skip the native tools and route via Make.com trigger from VAPI → fetch availability from GHL API → return slots → create appointment via a second Make step (this avoids silent failures in GHL writes). I can help you set this up cleanly end-to-end and debug what’s breaking in your current flow. Quick question: are you using a specific user calendar or a round-robin/team calendar in GHL? @Daniel Lee,