# Fix TimeZone issues writing to Google Calendar **URL:** \ **Category:** Ask for Help\ **Created:** [December 1, 2025, 1:48pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602 "2025-12-01T13:48:34Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jb\_1mprove](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jb_1mprove/32/92375_2.png) [@jb\_1mprove](https://community.glideapps.com/u/jb_1mprove)\ **Post date:** [December 1, 2025, 1:48pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/1 "2025-12-01T13:48:34Z")
Hey everyone, I know this question has similarly come up multiple times already over the years, but I couldn’t find a definitive answer anywhere yet. I’m running into the following issue: - I’m using the Email Trigger workflow (same issue in other workflows btw) - One of the columns is a datetime column. Let’s say that value in a certain workflow run is **07-11-2025, 11:00** - _Everywhere in the app, this looks good_. However, here comes the issue: - When pushing this date to **Google Calendar** , the event start datetime becomes 07-11-2025, **12:00** - I have managed to find a workaround in another workflow (using Zapier), but it’s not ideal and I want to have a robust way to make sure this works properly. !! For as far as I remember: every time I select the date myself from a date-time input, there is no issue. For that reason, I think it’s probably due to the workflow running server-side, but that still doesn’t tell me how to fix this. I’m in Europe/Amsterdam timezone, currently GMT+1. Hopefully some of you have some thoughts on this… 🙂 ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 1, 2025, 6:47pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/2 "2025-12-01T18:47:25Z")
Do you have Respect Timezone checked in your column? ---
**Author:** ![jb\_1mprove](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jb_1mprove/32/92375_2.png) [@jb\_1mprove](https://community.glideapps.com/u/jb_1mprove)\ **Post date:** [December 1, 2025, 6:48pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/3 "2025-12-01T18:48:56Z")
Yep, tried with and without. Both didn’t work ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 1, 2025, 7:34pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/4 "2025-12-01T19:34:36Z")
I think Glide stores date and time as if they were UTC +0 time regardless if they really are or not. I think they they always put the zulu code at the end. You may have to use a template column or math column to offset your date to account for that. I’d probably use a math column. You can use Format Date to get your offset, then divide that by 24 and add/subtract that value from your date column. Basically trick Google into using the correct time. ![1000006222](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/2/0/20146bdb45a935681fb3fbd4e817be21a05e41d8.jpeg) > [@I used the Google Calendar integration and facing issue with the Time that I filled with the time it is showing on the calendar](https://community.glideapps.com/t/i-used-the-google-calendar-integration-and-facing-issue-with-the-time-that-i-filled-with-the-time-it-is-showing-on-the-calendar/68405/7): > > I solved this problem, Solution to this problem is we can make a new column named “New Start Date” where we can use the concat(start time, -5:30) Gsheet formula in my GLide app column and now I can use this column which will update the desired time in the google Calendar. > [@Google Add Calendar Event start time always at 02:00 hour](https://community.glideapps.com/t/google-add-calendar-event-start-time-always-at-02-00-hour/81152/2): > > Under the hood, if I’ve understood things correctly, there is no such thing as only a date or only time. There are timestamps and a timestamp is a date and time in one object. And there are tons of difficulties related to timestamps (a date-time) because first these are displayed differently depending on region, device, etc. and second at a given timestamp (like “now”) the timestamp is are actually different based on where you are on the planet (time zones). I think that sums up the difficult… ---
**Author:** ![NFNHello](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nfnhello/32/3371_2.png) [@NFNHello](https://community.glideapps.com/u/NFNHello)\ **Post date:** [December 1, 2025, 7:53pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/5 "2025-12-01T19:53:47Z")
Disclaimers: I don’t remember if this was ever fixed, and I’m not certain on the impacted columns. As recently as December 2024, one of the date column types (format date, I think, but maybe it was the API v1) saved the time value in the user’s local time and appended the Z/zulu to the end of it making all sorts of issues. ---
**Author:** ![jb\_1mprove](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jb_1mprove/32/92375_2.png) [@jb\_1mprove](https://community.glideapps.com/u/jb_1mprove)\ **Post date:** [December 9, 2025, 4:42pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/6 "2025-12-09T16:42:44Z")
@Jeff_Hager @NFNHello Both of you, thanks a lot for your replies and effort to help. Due to other priorities, wasn’t able to get back to this and neither did I want to 😄. However, out of respect for your effort to help me, I dedicated the last hour to try again using your suggestions. Nonetheless, it didn’t work and this remains a major headache every time again. When using a user-selected date (client-side), no problem. But once a workflow is processing any date-time value server-side, it becomes a total nightmare. In conclusion: I’ve created a workaround using Zapier, because there I _can_ control what is sent to GCAL exactly. Thanks again for your help! PS. because here in the Europe/Amsterdam timezone we have varying offsets (+1 for winter, +2 for summer, I can’t hardcode a reliable fix using a math column) ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 9, 2025, 5:36pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/7 "2025-12-09T17:36:50Z")
> [@jb\_1mprove](#): > > PS. because here in the Europe/Amsterdam timezone we have varying offsets (+1 for winter, +2 for summer, I can’t hardcode a reliable fix using a math column) The format date column to calculate the offset should account for the winter/summer changes throughout the year. I believe it gets that offset directly from the device. > [@jb\_1mprove](#): > > But once a workflow is processing any date-time value server-side, it becomes a total nightmare. Good point, especially with the format date column. It would determine the offset from the server instead of the user device, which I assume the server is always GMT +0. You would probably have to do something where you calculate the offset datetime and store it in a basic column before running the server side workflow. I’m sure there is a little more to it based on your scenario, but that may be the root of your issue at the moment. ---
**Author:** ![jb\_1mprove](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jb_1mprove/32/92375_2.png) [@jb\_1mprove](https://community.glideapps.com/u/jb_1mprove)\ **Post date:** [December 9, 2025, 6:03pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/8 "2025-12-09T18:03:43Z")
@Jeff_Hager you’re right. That’s the issue. Since it’s running server-side, the offset column returns 0. I would need to add a bunch of columns or other logic to make this work reliably, so for now I’m sticking with the Zapier solution. Nonetheless, thanks a lot for your help! ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 9, 2025, 6:05pm UTC](https://community.glideapps.com/t/fix-timezone-issues-writing-to-google-calendar/85602/9 "2025-12-09T18:05:11Z")
Anytime