this is the call id

its not booking the appointment

it keeps checking availability but never returns the availability time

Thank you for confirming the calendar ID and timezone. To help pinpoint the issue, could you please share the exact

startDateTime

and

endDateTime

values you are using for the availability check in your GoHighLevel tool configuration? This will help us verify if the time range is set correctly, as this is a common cause of such issues. For reference, the required fields are: -

calendarId

-

startDateTime

(epoch time in milliseconds) -

endDateTime

(epoch time in milliseconds) -

timezone

You can find more details in the [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level). Source: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level)

To help resolve your issue, could you please share the exact error message or response you receive when the availability check fails? This detail will help pinpoint where the process is stumbling and allow for more targeted troubleshooting. For reference, please double-check that your

startDateTime

,

endDateTime

, and

calendarId

are set as described in the [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level). Source: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level)

To help resolve your issue, could you please share the exact error message or response you receive when the availability check fails? This detail will help pinpoint where the process is stumbling and allow for more targeted troubleshooting. For reference, please double-check that your

startDateTime

,

endDateTime

, and

calendarId

are set as described in the [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level). Source: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level)

Thank you for confirming your configuration and providing the call ID. To help us narrow down the issue, could you please let us know: Are you seeing any specific error codes or detailed error messages in the Vapi Dashboard or logs when the availability check fails, or does it only say "couldn't check the availability or no availability"? This will help us determine if the problem is with the integration setup or something else. For reference, you can review the [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level) for required configuration steps. Source: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level)

Thank you for confirming your configuration and providing the call ID. To help us narrow down the issue, could you please let us know: Are you seeing any specific error codes or detailed error messages in the Vapi Dashboard or logs when the availability check fails, or does it only say "couldn't check the availability or no availability"? This will help us determine if the problem is with the integration setup or something else. For reference, you can review the [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level) for required configuration steps. Source: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level)

Try this actionable step: Double-check that your GoHighLevel "Check Availability" tool is configured with a valid time range that actually includes available slots. For example, set the time range to cover the entire working day in your timezone:

json
{
  "calendarId": "PT3GKbFAlidEtpPMGHPU",
  "startDateTime": 1716681600000,
  "endDateTime": 1716768000000,
  "timezone": "America/New_York"
}

If the issue persists even with a wide time range, please share the exact time range values you are using so support can investigate further. [See GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level) Source: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level)

Try this actionable step: Double-check that your GoHighLevel "Check Availability" tool is configured with a valid time range that actually includes available slots. For example, set the time range to cover the entire working day in your timezone:

json
{
  "calendarId": "PT3GKbFAlidEtpPMGHPU",
  "startDateTime": 1716681600000,
  "endDateTime": 1716768000000,
  "timezone": "America/New_York"
}

If the issue persists even with a wide time range, please share the exact time range values you are using so support can investigate further. [See GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level) Source: - [GoHighLevel Integration Documentation](https://docs.vapi.ai/tools/go-high-level)

looking into it.

First attempt (failed due to missing timezone). Subsequent attempts (with complete payload: The GoHighLevel API is returning a response that only contains a traceId field and no date-specific keys. This means: 1. The API call is succeeding (no error is thrown) 2. The response contains only { traceId: "some-id" } 3. After filtering out traceId, there are no date-specific keys left 4. This triggers the "No available times found" response Potential Issues: 1. **Calendar Configuration**: The calendar might not have any business hours configured or available slots. 2. **Date Range Issue**: The dates being checked (May 2025) might be: - Too far in the future for the calendar's configuration - Outside the calendar's configured availability window - In a date range where no slots are actually configured - **Permission/Scope Issue**: The integration might not have proper read permissions for the calendar's availability data. - **GoHighLevel API Behavior**: The calendar might exist but have no configured availability slots or business hours. Recommended Investigation Steps: **Verify Calendar Configuration**: Check in GoHighLevel if calendar has: - Business hours configured - Available time slots defined - Proper calendar settings **Test with Different Date Ranges**: Try checking availability for: - Current week instead of May 2025 - Different time ranges to see if the behavior changes

Karthick let me know your thoughts on this.