Create Google Calendar event | Daylight savings issue

Questions
,
1

:bullseye: What is your goal?

Create a future Google Calendar event that will account for Daylight Savings time.

:thinking: What is the problem & what have you tried?

When the event is created before DST, the time is incorrect once DST has occurred. The scenario runs by gathering date and time data from a Google Sheet, formats the data, and then creates a Google Calendar event. The problem occurs when the event creation occurs during Standard time but the event date is during Daylights Savings time. Once DST happens, everything on the calendar is off by an hour. (and vice versa). How can I circumvent this?

Screenshots included.

image
image1310Ă—763 182 KB

image
image739Ă—889 56 KB

image
image1128Ă—883 91.8 KB

3

Hi and welcome to the Community!

By using the parseDate function with a hardcoded timezone like America/Chicago, you are forcing the system to interpret the date-time string based on the current offset of that timezone at the moment the scenario runs, rather than the offset that will exist on the target date.

To fix this, you need to stop parsing the date manually into a specific timezone string and instead let Google Calendar handle the UTC conversion.

In your Tools module (Item 12 & 13), you are concatenating a Date and Time and then using parseDate with a specific timezone.

  • The Flaw: parseDate creates a “Date Object.” When Make passes this object to Google Calendar, it often translates it to UTC based on the current date’s offset (Standard Time).

  • The Result: If it’s currently March 1st (CST) and you’re booking for July 1st (CDT), the system applies the -6 hour offset instead of -5.

The most reliable way to handle DST in Google Calendar is to provide a single string in ISO 8601 format that includes the date and time, and then let the Google Calendar module itself handle the timezone.

1. Update your Tools Module (Variable Value)

Change your Start_DateTime and End_DateTime variables to simply format the string into a standard format without parsing it yet. Use this logic:

formatDate(8.Start_Date; YYYY-MM-DD)TformatDate(8.Start_Time; HH:mm:ss)

  • Note: Use a capital T between the date and time. This creates a string like 2026-07-01T14:00:00.

  • Do not wrap this in parseDate yet.

2. Update the Google Calendar Module

In your Google Calendar “Create an Event” module, map your variables directly into the Start/End date fields.

  • Start Date: parseDate(9.Start_DateTime; YYYY-MM-DDTHH:mm:ss; America/Chicago)

  • End Date: parseDate(9.End_DateTime; YYYY-MM-DDTHH:mm:ss; America/Chicago)

5

Thank you so much for your help with this. I have made the suggested changes, but unfortunately will not really know if it works until DST changes again. I will try to remember to offer an update on this if it works.

1 Like
6

Yh the solution DavidGurr_Make Provided would definetely work but unfortunately you did implement it after DST changes

1 Like