Issue with Google Calendar Invite - Timezone Setting

[Sujatha V M]

Hello All, 

I'm currently facing an issue where the Google calendar invite get created upon an approval from ServiceNow. The invite gets created without any issues on the respective date. 

On the request body contains the timezone is also set as "US/Eastern" (including the local setting) whereas the response contains the timezone as "America/New York", but the timings are 6+ hours ahead of whats been passed on. 

Eg. If 10 AM is selected, the calendar invite should be created with the timings as 10 AM but it shows as 5PM as start time. 

Any help on this would be appreciated. 

[Ankur Bawiskar]

@Sujatha V M 

are you consuming any endpoint and sending the time?

If yes then it's definitely because of the timezone difference.

if 10 AM is selected but in which timezone? the logged in user's?

share some screenshots etc

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Sujatha V M]

@Ankur Bawiskar Thank you for the response. 

Yes, Google Calendar is integrated with ServiceNow and uses an endpoint URL which holds the calendar ID for event creation. 

Logged in user profile is set as "US/Eastern" timezone and it's 10 AM EST. 

Request Body Log  : 

Google Calendar Integration - Request Body: {"summary":"CHG00XXXXX","start":{"dateTime":"2025-06-23T10:00:00.000Z","timeZone":"US/Eastern"},"end":{"dateTime":"2025-06-23T10:30:00.000Z","timeZone":"US/Eastern"}}

Response Log : 

"start": {
"dateTime": "2025-06-23T06:00:00-04:00",
"timeZone": "America/New_York"
},
"end": {
"dateTime": "2025-06-23T06:30:00-04:00",
"timeZone": "America/New_York"
},

Google calendar timezone settings : (GMT - 4) Eastern Time - New York

Both the timezones are same but still it doesn't reflect the timings but sets the date fine and its converted into ISO format.

[Ankur Bawiskar · Accepted solution]

@Sujatha V M 

it's definitively timezone issue.

Did you check the API docs?

[Sujatha V M]

@Ankur Bawiskar  Thank Ankur! I have fixed the issue! It was because of the default UTC timezone!