Intregrating Google Calendar, which time should I use in parameters

[Muhammad_Qasim2]

In the Google Calendar, creating event node, which time zone should I add to the start and end time of the event???

[Anshul_Namdev]

Hi @Muhammad_Qasim2
Set your workflow timezone to match the timezone of your Google Calendar events, and then the node will automatically use that timezone for start or end time. This mostly happens when the workflow timezone is not set properly to the user’s preference.

See this:

Outlook event created at the wrong time (1 hour later)

Hello ! I’m working on an agent to manage my Outlook calendar through Telegram chat, and I’ve some issues when trying to create event.… Describe the problem/error/question I’ve a main agent and a sub agent which is dedicated to calendar. When I try to create an event (for example at 8AM), the agent tells me that the event has been created but in Outlook, the event is created at 9AM. If I ask the agent the list of events, the agent will again tell me that it is at 8AM. Of course, I’ve told t…

[tamy.santos]

good day @Muhammad_Qasim2
We had a similar case in the community recently where the server timezone ended up interfering with the event time. In n8n, timezone handling can be affected by three layers: the value sent in the Google Calendar start and end fields, the workflow or instance timezone configured in n8n, and, for self-hosted setups, environment variables such as GENERIC_TIMEZONE and TZ. So if the server is running in a different timezone, for example UTC, and the workflow sends a datetime without an explicit offset like 2026-05-08T10:00:00, n8n or Google Calendar may interpret it differently than expected. I’d review those three layers and share what you find.