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.
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.
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.
