Subhashish Jung Shah
10/01/2024, 2:24 PMVapi
10/01/2024, 2:25 PMYYYY-MM-DDTHH:MM:SSZ for UTC times.
2. Specify the Time Zone: When creating events in Google Calendar, explicitly set the timeZone property to 'UTC' for both start and end times to make sure Google Calendar interprets the times as UTC.
3. Convert to Google Calendar Format: If necessary, convert the timestamp from the VAPI function to the RFC3339 format before sending it to the Google Calendar API.
4. Test with Static Data: Try creating an event with static UTC times to confirm that the issue is with the timestamp format or conversion.
5. Check the API Documentation: Review the Google Calendar API documentation to ensure that all required fields are being set correctly and that there are no additional settings that might affect time zone handling.
6. Log and Inspect API Requests: Log the API requests being made to the Google Calendar API and inspect them to ensure that the data being sent is in the correct format and that no unintended transformations are occurring.
If you've already checked these aspects and the problem persists, it might be helpful to provide a specific example of the timestamp you're receiving from the VAPI function and how you're passing it to the Google Calendar API. This way, I can give you more targeted advice. If you need further assistance with the VAPI function itself or have other questions, please let me know!Vapi
10/01/2024, 2:25 PMShubham Bajaj
10/03/2024, 1:23 PMSubhashish Jung Shah
10/03/2024, 1:25 PMShubham Bajaj
10/03/2024, 10:02 PMSubhashish Jung Shah
10/04/2024, 1:27 AMShubham Bajaj
10/04/2024, 7:50 PM