I'm trying to get Workflows to interact with GHL Calendars and check availability and create appointments. I've tested the APIs in my application directly and those are all working fine, but when I try to run a call through VAPI it's not hitting the tools, and also refuses to automatically hang up the call. Any tips much appreciated. one example call 06f1db6d-47e0-45ab-b8eb-5733eebabb3a

Thanks for sharing the details! To help you further, could you clarify whether your workflow includes the "Hangup" node at the end and if all GoHighLevel tools are properly added and published to your assistant? This will help pinpoint if the issue is with workflow configuration or tool integration. Sources: - [GoHighLevel Tools for Calendar and Contact Management](https://docs.vapi.ai/tools/go-high-level) - [Workflows Quickstart](https://docs.vapi.ai/workflows/quickstart) - [Hangup Node Usage](https://docs.vapi.ai/workflows/nodes/hangup)

Yes, it has a hangup node No, it does not have tools because it's a workflow... my understanding is workflows do not use assistants as they are different use cases

Add all four GHL tools with correct IDs, define the usage clearly in the system prompt using exact tool names, and include an "End Call" node to ensure the call disconnects properly..

What if I am passing in a GHL contact id already? I am using a GHL webhook to hand a contact into a nextjs app which is creating workflows etc with the API. I don't need the create/get contact tools because I know the contact, but the check availability/create event tools are silently failing

Use the known contactId, ensure calendarId and timezone are valid, pass startDate/endDate in epoch ms for availability and ISO format for event creation, and use GHL’s calendar troubleshooting tool to check for conflicts or blocked slots causing silent failures..

How can I get diagnostic information from the tools themselves in the workflows? It's hard to pin down what is happening, the tools are not firing at all. Tried disconnecting GHL and connecting via oauth at the subaccount level and that didnt help. Related - does agency-level oauth work? My use case would have multiple subaccounts ideally

Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue

I am having trouble getting the tool to pass the required locationID parameter to schedule the appointment. It worked once, but I can't seem to get the tool to include it in the payload. I'm creating these tools via the API, so I must have something misconfigured

In your tool configuration, ensure that the 'locationId' parameter is marked as required.