@Eric Chong | HSFM I'm sorry to hear you're experiencing issues with date variables in Make.com when using VAPI. It's important to ensure that the date format and variables you're using are compatible with VAPI's expected input. If you're having trouble with dynamic variables or the date is not being passed correctly, it might be due to a formatting issue or a misconfiguration in your Make.com scenario. To assist you better, could you please provide more details about how you're trying to pass the date to VAPI? Are you using a specific function within VAPI that requires a date parameter? Knowing this will help me guide you through the correct process. Regarding your credits, typically, transferring credits between accounts is not a standard procedure. However, if you believe there's an issue with your current account, I recommend reaching out to our support team directly. They can look into your account specifics and provide a solution tailored to your situation. Would you like me to help you contact support?

You have some time to hop on a screen share. I had these problema few times and help some others as well.

yes, that would be great

@Eric Chong | HSFM I'm glad to hear you're willing to help others with similar issues. However, as a text-based support bot, I'm unable to participate in screen shares or live sessions. But I can certainly guide you through the process of troubleshooting the issue with the date being passed through webhooks. If the date being passed is incorrect, such as always defaulting to October 2023, it's possible that there is a static value set somewhere in your Make.com scenario or that the date format is not being recognized by VAPI. Here are a few steps you can take to troubleshoot the issue: 1. Check the Date Variable: Ensure that the variable you're using for the date in Make.com is dynamic and correctly formatted. It should reflect the current date or the date you intend to pass to VAPI. 2. Date Format: Verify that the date format matches what VAPI expects. Different systems may require dates in different formats (e.g.,

YYYY-MM-DD

,

MM/DD/YYYY

, etc.). 3. Webhook Configuration: Look at the webhook configuration in Make.com to ensure that it's set up to pass the correct data to VAPI. 4. Test the Scenario: Run a test scenario in Make.com and check the output logs to see what data is being passed. This can help you identify where the incorrect date is coming from. 5. Documentation: Review VAPI's documentation to ensure you're using the correct syntax for dynamic variables and that your webhook is configured to use them properly. If you've gone through these steps and are still facing issues, it might be best to reach out to Make.com's support for further assistance, as they can provide more detailed guidance on their platform's functionality. Regarding the booking of an appointment, if you have the correct date and are ready to proceed with booking through VAPI, please provide the necessary details such as the appointment date, time, and any other relevant information, and I can assist you with the next steps.

I've tried all this but it's still failing to pass the right time.

Hey @Eric Chong | HSFM 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!

Hi Shubham, sorry I was traveling, but i got this figured out finally, thank you

What did you do to figure this out?