I’m encountering an issue with the VAPI and Make.com integration for booking appointments in a GHL sub-account. I’ve set up a scenario in Make.com, where one of the modules sends data back to VAPI to confirm whether the appointment was booked or if slots are unavailable. While everything works perfectly in Make.com, the issue appears to be on the VAPI side. Sometimes VAPI triggers the Make.com scenario without capturing the appointment details. Other times, an appointment is booked through the Make.com scenario, but VAPI incorrectly states that no slots are available and asks to choose a different time. I tried following the flow when VAPI says that the slots are unavailable, and I selected the dates VAPI offered. However, even after selecting the VAPI-provided dates, it triggered the automation again and responded that the chosen dates were still not available, despite the new date being chosen. If anyone has a workaround or tips for resolving this, I’d really appreciate it. I’m on the verge of looking for an alternative platform if this issue persists. Thanks in advance!

Heyval Thank you for creating the ticket! A member of our team will reach out to you shortly.

yaah, i would really appreaciate the help please

@val I'm sorry to hear that you're experiencing issues with the VAPI and Make.com integration. It sounds like there might be a synchronization problem between VAPI and the Make.com scenario, or there could be a misconfiguration in the way VAPI is handling the appointment details and availability. To help you resolve this issue, here are a few steps you can take: 1. **Check the Configuration**: Ensure that the VAPI is correctly configured to send and receive the correct data to and from Make.com. Double-check the data fields and make sure they match on both platforms. 2. **Logs and Debugging**: Look into the logs on both VAPI and Make.com to see if there are any errors or warnings that could give you more insight into where the process is failing. 3. **Communication Flow**: Review the communication flow as outlined in the documentation to ensure that the data is being passed correctly at each step of the process. 4. **Webhook Settings**: Verify that the webhook settings in VAPI are set up correctly to trigger the Make.com scenario with the right conditions and data. 5. **Test with Static Data**: Try testing the integration with static data to see if the issue persists. This can help isolate whether the problem is with dynamic data handling. 6. **Contact Support**: If you've gone through these steps and the issue still isn't resolved, it might be best to reach out to VAPI support for more in-depth assistance. Remember, it's important to ensure that the data being passed between VAPI and Make.com is consistent and that any conditional logic in your scenario is correctly set up to handle different outcomes. If you need further assistance with checking the configuration or logs, or if you have any other questions, please let me know, and I'll do my best to assist you.

i think i have all the above things right, despite having the issue, id like to speak with the support if its possible

I am also facing the same issue, the make.com is creating the webhook body and status code correctly, but it is not sending any output file to VAPI, since no output data is sent, VAPI is not considering those data. Please help me to resolve this issue https://cdn.discordapp.com/attachments/1335308574556946480/1335616558403289188/image.png?ex=67a0d15a&is=679f7fda&hm=ae2feb15f4512793cd0f5ccf7d963084e82caf5ea8b7fe48194e371ac623c108&

@Ayan Das I understand that both of you are facing similar issues with the VAPI and Make.com integration. It seems like the problem might be related to the way the webhook is configured or how the data is being processed by VAPI after it's received from Make.com. Since you've already checked the configuration and the issue persists, it would be best to escalate this to our support team for a more in-depth investigation. They will be able to look into the specifics of your setup and provide a tailored solution. I will go ahead and notify our support team to reach out to you as soon as possible to help resolve this issue. Please hold on while I do that.

Hey @val 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 me figure out what went wrong!

@Shubham Bajaj Thanks for the quick response, I figured out the issue, for me it was a time zone adjustment issue in the make flow. It is working fine for me now.

@val Because of no response closing this ticket.