GHL Tools not working
# support
f
Hey, I am writing to report a problem I am experiencing with VAPI and its GHL native tools. They are currently not working. Could you please help me solve this issue? Thank you for your time and attention to this matter. https://cdn.discordapp.com/attachments/1372267379177816145/1372267379576541304/image.png?ex=68262716&is=6824d596&hm=db8e50ef2b1997aeae7c0e47b5ea935dd75533576964da6f758049a0ce8faa11&
v
A common issue with Vapi's GHL native tools is incorrect JSON response formatting, which can cause actions like "Calendar Create Event" to fail. Please ensure your tool's response matches this structure:
Copy code
json
{
  "results": [
    {
      "toolCallId": "call_29386782601936",
      "result": {
        "message": "The preferred appointment time is unavailable, I have the following timeslots",
        "slots": {
          "2025-01-14": [
            "2025-01-14T15:30:00-05:00",
            "2025-01-14T17:00:00-05:00"
          ]
        }
      }
    }
  ]
}
Double-check your integration's output and try again—this often resolves tool execution issues in Vapi ([source](https://discord.com/channels/1211482211119796234/1327481613004701779)). Source: - [Discord: Vapi GHL native tools troubleshooting](https://discord.com/channels/1211482211119796234/1327481613004701779)
f
@Vapi Support Bot where do I see that?
v
To view the Vapi tool response, go to the Vapi Dashboard and use the left sidebar to navigate to Logs > Calls. Find the relevant call and copy its "call ID"—the call logs will display the tool responses, including the JSON output you need. There is no separate tool response view; all responses are shown within the call logs for each call. Source: - [Discord: Vapi tool response location](https://discord.com/channels/1211482211119796234/1325000684231196775)
k
Hey, Could you please schedule a brief call at your convenience so we can discuss this matter in detail? Kindly use the following link to book a suitable time: .
k
did this get resolved? I have the same issue.
k
Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
2 Views