@dhoklaboy
It sounds like there might be a discrepancy between the time settings in your VAPI prompt and the webhook response received by make.com. Here are a few things to consider that could help resolve the issue:
1. Timezone Configuration: Ensure that both the VAPI prompt and make.com are configured to use the CST timezone explicitly. Sometimes systems default to UTC or another timezone if not specified.
2. Time Synchronization: Check if the servers hosting your VAPI prompt and make.com are synchronized with an accurate time source. This ensures that both systems are operating on the correct current time.
3. Date Formatting: Verify that the date format used in the VAPI prompt matches the expected format on make.com. Differences in date formatting can lead to misinterpretation of the dates.
4. Webhook Configuration: Review the webhook configuration to ensure that it is correctly handling the timezone. It should either convert the time to the local timezone or pass the timezone information along with the time.
5. Check for Delays: Sometimes network delays or processing times can cause timestamps to appear different than expected. Ensure that there are no such delays affecting the time calculations.
6. Documentation Review: Double-check the documentation for both VAPI and make.com to ensure that you're implementing the timezone handling as recommended by both services.
7. Testing: Conduct tests by sending known timestamps from VAPI to make.com and see how they are processed. This can help identify where the discrepancy is occurring.
If you've gone through these steps and are still experiencing issues, it might be helpful to reach out to the support teams for both VAPI and make.com for further assistance. They may be able to provide more insight into the problem based on their system logs and configuration details.