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

[Difnet]

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 to agent what is the date, and I’ve mentioned that events must be created in Paris time zone.

What is the error message (if any)?

No error, just wrong time

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version: 1.120.3
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system:

Do you have an idea about the issue and how to fix it ? I think that I need to fix the time zone but where should it be defined ?

Thank you !

[Parintele_Damaskin]

Hey @Difnet !

You will need to set the Timezone to something like Europe/London for example.

If you share your ENV variables(global assignment) we can have a look and be more specific.

You can also set it in the workflow settings (top right 3 dots-> settings to open those)

Workflow could not be activated due to invalid timezone

Hi @CUBEevo_AD You probably set the timezone of your n8n server to UTC or something similar, this is not correct so it gives you the error that it is invalid. You will need to set the Timezone to something like Europe/London for example. If you share your ENV variables we can have a look and be more specific. You can also set it in the workflow settings (top right 3 dots-> settings to open those) [image]

[Mutasem]

What’s your instance’s timezone configured to? If using Cloud, then this will be configurable in the admin panel. If self-hosted, you can set environment variable.

As @Parintele_Damaskin also mentioned you can also set the timezone for the workflow. Check all of these and what the expression resolves to in the node parameters.

[Difnet]

Thanks to both of you.
By defining time zone in the workflow settings (I was not aware about this setting), it seems to have fixed the issue.
Just to be sure, I’ve also forced time zone in additional field of Outlook create event action. After few tests, it sounds good in all cases.

Thanks so much for your help !