eastern-cyan•4mo ago
Time error while google calendar integration
Hey i integrated google calendar with vapi but after booking an appointment its showing wrong time in google calendar the date is correct only issue is with time , in calendar time zone its america Chicago in vapi agent prompt its the same then why the error coming up? Can anybody help me
6 Replies
Thanks for sharing the details! To help diagnose the issue, could you confirm whether the
startDateTime
and endDateTime
values you are sending to the Google Calendar integration are in ISO 8601 format and explicitly include the "America/Chicago" timezone? This will help narrow down if the problem is with the datetime formatting or the timezone handling.
If you need more guidance, the Vapi Google Calendar integration documentation has best practices for time zone handling.
Source:
- Vapi Google Calendar Integration Documentation⤵️ Mention @Vapi Support Bot for follow-ups 🐥
eastern-cyanOP•4mo ago

eastern-cyanOP•4mo ago
Please Check my prompt
To help resolve the time error:
Could you please share the exact
Could you please share the exact
Make sure that when you trigger
Reference: Vapi Google Calendar Integration Documentation Source: - Vapi Google Calendar Integration Documentation Suggestion:
Make sure that when you trigger
Reference: Vapi Google Calendar Integration Documentation Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure your assistant's prompt or tool configuration explicitly sets the
See Vapi Google Calendar integration best practices. Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure your assistant's prompt or tool configuration explicitly sets the
See Vapi Google Calendar integration best practices. Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure when creating the Google Calendar event you explicitly set both the
See best practices in the Vapi Google Calendar integration documentation. Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure when creating the Google Calendar event you explicitly set both the
See best practices in the Vapi Google Calendar integration documentation. Source: - Vapi Google Calendar Integration Documentation
Could you please share the exact
startDateTime
, endDateTime
, and timeZone
values that are being sent to the Google Calendar integration when the event is created? This will help determine if the issue is with the datetime formatting or the time zone handling.
For reference, all datetime fields should be in ISO 8601 format and the timeZone
should be explicitly set to "America/Chicago" as per the Vapi Google Calendar integration documentation.
Source:
- Vapi Google Calendar Integration Documentation
To help resolve the time error:Could you please share the exact
startDateTime
, endDateTime
, and timeZone
values that are being sent to the Google Calendar integration when the event is created? This will help determine if the issue is with the datetime formatting or the time zone handling.
For reference, all datetime fields should be in ISO 8601 format and the timeZone
should be explicitly set to "America/Chicago" as per the Vapi Google Calendar integration documentation.
Source:
- Vapi Google Calendar Integration Documentation
Suggestion:Make sure that when you trigger
google.calendar.event.create
, you are passing the startDateTime
and endDateTime
fields in ISO 8601 format and explicitly include the "America/Chicago"
timezone in the timeZone
field of the payload. For example:
This ensures Google Calendar interprets the time correctly. Double-check that your prompt and tool logic are not just mentioning the timezone, but actually passing it in the event creation call.Reference: Vapi Google Calendar Integration Documentation Source: - Vapi Google Calendar Integration Documentation Suggestion:
Make sure that when you trigger
google.calendar.event.create
, you are passing the startDateTime
and endDateTime
fields in ISO 8601 format and explicitly include the "America/Chicago"
timezone in the timeZone
field of the payload. For example:
This ensures Google Calendar interprets the time correctly. Double-check that your prompt and tool logic are not just mentioning the timezone, but actually passing it in the event creation call.Reference: Vapi Google Calendar Integration Documentation Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure your assistant's prompt or tool configuration explicitly sets the
timeZone
field to "America/Chicago"
when creating the Google Calendar event. For example, ensure your event creation payload includes:
This ensures Google Calendar interprets the time correctly. Double-check that your prompt or backend logic always passes the correct timezone value when scheduling events.See Vapi Google Calendar integration best practices. Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure your assistant's prompt or tool configuration explicitly sets the
timeZone
field to "America/Chicago"
when creating the Google Calendar event. For example, ensure your event creation payload includes:
This ensures Google Calendar interprets the time correctly. Double-check that your prompt or backend logic always passes the correct timezone value when scheduling events.See Vapi Google Calendar integration best practices. Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure when creating the Google Calendar event you explicitly set both the
startDateTime
and endDateTime
in ISO 8601 format and include the timeZone
field as "America/Chicago"
. For example:
Double-check that your assistant's code or tool call includes these fields as shown above to ensure the correct time is reflected in Google Calendar.See best practices in the Vapi Google Calendar integration documentation. Source: - Vapi Google Calendar Integration Documentation Suggestion:
To avoid time errors, make sure when creating the Google Calendar event you explicitly set both the
startDateTime
and endDateTime
in ISO 8601 format and include the timeZone
field as "America/Chicago"
. For example:
Double-check that your assistant's code or tool call includes these fields as shown above to ensure the correct time is reflected in Google Calendar.See best practices in the Vapi Google Calendar integration documentation. Source: - Vapi Google Calendar Integration Documentation
eastern-cyanOP•4mo ago
Already done still same
In google sheets everything is fine its only happening in google calendar
Ensure all tools use the exact same time zone and ISO 8601 date-time format without conflicting offsets.