Hey everyone! I'm trying to send the available timeslots from my Go High Level calendar to VAPI using a webhook. The Make.com workflow runs smoothly — the HTTP module correctly retrieves the available timeslots. However, VAPI doesn't seem to understand the webhook data, or maybe it’s not receiving it at all. Even though the times are clearly available, it keeps saying they aren’t. It seems like it's unable to interpret or confirm the information, even though I’ve prompted it correctly. Could anyone help me figure out what’s going wrong? Could it be that my webhook isn’t properly configured? (In the screenshot, the timeslots are properly formatted, and when I test the workflow, I can see all the available times from the calendar. But VAPI still can’t confirm or recognize the data being sent.) Thanks in advance! https://cdn.discordapp.com/attachments/1356638279356907632/1356638279675674664/image.png?ex=67ed4b5a&is=67ebf9da&hm=3796c871858a4643defa551bb7a034958e6ad46627904e80b185e8ebab4df929&

Hi there! 👋 I see you're having trouble with VAPI not understanding the timeslot data from your Go High Level calendar webhook. I'm unable to provide specific information about the "disponible" field in your webhook configuration as I don't have details on that. However, I can definitely help with the timeslot formatting issue and webhook configuration! Based on the information I found, here are some likely issues and solutions: ## JSON Format Issues The most common reason VAPI doesn't understand timeslot data is incorrect JSON formatting. Your webhook response should follow this structure:

json
{
  "results": [
    {
      "toolCallId": "call_ID_FROM_VAPI_REQUEST",
      "result": "The following timeslots are available: 2025-01-31T14:00:00-05:00,2025-01-31T14:30:00-05:00,2025-01-31T15:30:00-05:00"
    }
  ]
}

According to [troubleshooting documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334658296291921920), the

toolCallId

in your response must match the ID sent by VAPI in the initial request. ## Date Formatting I notice in your screenshot that you're using "Format Now Date" which might be causing issues. For timeslots, VAPI expects ISO 8601 format with timezone information (e.g.,

2025-01-20T09:00:00+01:00

). According to [best practices for formatting timeslot data](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336772166330351646), you can use the

date

filter in Make.com with format specifiers and timezone:

{{"now" | date: "%Y-%m-%dT%H:%M:%S%z", "America/New_York"}}

## Webhook Configuration Make sure your webhook is properly configured: 1. Set the Content-Type header to

application/json

in your Make.com HTTP module 2. Ensure you're capturing the

toolCallId

from VAPI's request and including it in your response 3. Check that your response structure matches what VAPI expects

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!

Your json isn't formated well

Thank you i will try that

Message marked as helpful by @Alexan! 🎉

It's still not working even with your JSON. I put the caller ID and my timeslots, and the assistant keep telling 'time not available' when it is. Whats bizarre is that he gives me other timeslots, and the second one I choose, even though it says ''also not available'' it proceed with my second workflow and book the appointment to this date & time. For my date formatting string, its just a formatting so it understand and update the timeslots string to ''now'', otherwise its stuck at past date and can't retreive timeslots. As you can see in the picture, the webhook fetch the timeslots properly. https://cdn.discordapp.com/attachments/1356638279356907632/1357029012681003078/image.png?ex=67eeb741&is=67ed65c1&hm=9321f5686e7d8a8f7bf3a54a285537269322f50ee118235df448ebb24e2aefaf&

Hi, checking if this is resolved/solved for you?

Not resolved, the webhook structure still doesnt work, the assistant failed to confirmed the available time slots when i choose one.

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!