I am now having some issues with the google calendar get availibility node, it seems to run the flow and create booking events, but it does not recognize already booked events within that time slot, it will still book them, my idea is to only allow 36 booked events within a time slot, even if that time bleeds into another, if the user says 6:30 but 35 events are booked for 6:30 and one more event still continues from 5:30 into 7:30, then 6:30 isnt sufficient, but it has trouble even recognizing one event at the moment

Thank you for describing your issue. To help diagnose the problem: Could you confirm if your "get availability" node is configured to check for overlapping events within the entire time range (including events that start before and end after the requested slot), and are you using any custom logic to enforce the 36-event limit per slot? This will help determine if the issue is with the tool's configuration or if additional logic is needed. Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)

Thank you for sharing your configuration details. To help pinpoint the issue: Can you confirm if your availability check is set to include events that start before and end after the requested time slot (i.e., overlapping events), or is it only checking for events that exactly match the slot? This will clarify if the node is missing "bleeding" events that overlap with your requested time. If possible, please specify how your time range is defined for the availability check. Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)

how do i check that

To help you check if overlapping events are being considered: Can you review your "get availability" node and confirm if the time range (

startDateTime

to

endDateTime

) fully covers the slot you want to check—including any events that might start before and end after your requested time? If you're unsure where to set this, please let me know if you see any options for "time range" or "include overlapping events" in your node configuration. For reference, the [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar) states that the availability check uses the specified start and end times to determine conflicts, so ensuring your time range is broad enough is key. Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)

i dont have the option for "time range" or "include overlapping events" start time and end time are defined automatically by the model

Suggestion: To ensure overlapping events are detected, try manually setting the

startDateTime

and

endDateTime

fields in your "get availability" node to explicitly cover the full time slot you want to check (e.g., 6:00–7:00 for a 6:30 request). This can often be done by overriding the automatic values with dynamic expressions or variables in your workflow tool. If your node does not allow manual input, consider adding a step before the availability check to calculate and set these values explicitly. This approach helps the availability check catch any events that "bleed" into your requested slot, as recommended in the [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar). Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)

so like this: start time: {{ $('Webhook').item.json.body.message.toolCalls[0].function.arguments.date }} end time: {{ $now.plus(1, 'hour') }}

Thank you for sharing your approach. After setting the

start time

and

end time

manually as shown, does the "get availability" node now correctly detect overlapping events, or are you still seeing bookings created during already-occupied slots? This will help determine if further adjustments are needed in your workflow configuration. Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)

now it says it has trouble accessing the calendar

Suggestion: When you see "trouble accessing the calendar" after updating your node, double-check that your Google Calendar connection is still valid and authorized. In your workflow tool, re-select the correct Google Calendar account and re-authenticate if prompted. If the issue persists, try removing and re-adding the Google Calendar credential, then test the node again. This step often resolves access errors after configuration changes ([Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)). Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)

is there a way i could speak with a vapi agent

To speak with a Vapi agent, the fastest way is to join the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) and post your request in the #support channel for real-time assistance. Alternatively, you can email support@vapi.ai, but Discord typically offers quicker responses for technical issues or live help. Source: - [Vapi Support Options](https://docs.vapi.ai/support)