Howdy folks!
If you’ve been having trouble using Google Calendar in your time zone, here is a trick that might help!
What you’ll need:
- Google Calendar
- Coda doc with Google Calendar Pack installed
- Table in Coda, with a column formatted as “Google Calendar - Event” containing event URLs
At first, your Table may look like this:
Let’s add a Start and End column, but with a twist; we’ll add Hours(3), to shift the times from Pacific to Eastern:
(If you are in a different timezone than Eastern Time, use the appropriate number of hours offset from Pacific Time)
I hope this trick helps for the time being, and note that we are also working on adding timezone support to Coda, so stay tuned! 
Josiah Krutz
3 Likes
Hi,
Is there any way to create a recurring reminder / block off time on a daily basis on the calendar?
Want to create a recurring/daily reminder for a coda document that I’m building. It’s essentially a daily journal template.
This is not sufficient. There are periods in a year when the hour differential between two time zones is not the same as the rest of the year. We’re in one of those periods now (Mar 19, 2025 – US Central is 6 hours from Berlin, but most of the year it’s 7 hours). We need to be able to specify the time zone of the google calendar event from Coda.
@silviana_amethyst
as per this thread Time zone madness, daylight saving, and Google Calendar events
the daylight savings issue is a google calendar issue. gcal doesnt buffer in the time changes and its on the onus of the event creator to account for the daylight savings time.
Cheers!
Mel
Hi @Melanie_Teh , thanks for your time and help.
I guess, I would really like to let my users be able to say “9am in US Central on March 20, 2025”, and not have to think about it. I use Fantastical / iCal and it just does this for me. I don’t have to personally think about daylight savings. Similarly, I can in Google Calendar specify the same. I tested it: I made an event in Google Calendar “9am in US Central on March 20, 2025”, and it shows up in Coda correctly in Berlin time with an offset of 6 hours (cuz we’re in the period when Europe and US are out of sync), instead of 7. Similarly, an event on July 1, 2025 at 9am in US Central comes in at 4pm Berlin, correctly.
I guess, with what’s provided, my users MUST know what time in the Coda Doc timezone the event occurs when they make the Coda row. in which case I don’t need to do anything about time zones, a human does it all. It’s just a lot to ask of my entire team to have to deal with daylight savings and always convert to one time zone, regardless of what it is, as it requires perfect memory.
I agree that the other thread I’ve been writing in is now more on-topic – but I maintain that a problem would be solved if I could make events in gcal from Coda and specify the time zone. The GCal API allows it… And it would be even more solved if time zones and time zone conversions were natively supported in Coda.
Thanks again for your time and help.
~silviana
