Default timezone in n8n workflow
- Feb 13
- 1 min read
What this means (non-technical)
If a workflow does not explicitly define a timezone, it uses the server’s default timezone. If the server timezone changes, the workflow’s execution time shifts with it.
This can happen during migrations or infrastructure changes.
What usually goes wrong
After moving to a new server or environment:
Scheduled workflows run hours earlier or later.
Daily reports use the wrong date boundaries.
Notifications are sent at unexpected times.
Because nothing appears broken, the timing shift can go unnoticed for days.
Timezone issues are often confusing and difficult to diagnose.
When this becomes urgent
This becomes urgent when:
You migrate servers.
You run workflows across multiple regions.
Daylight saving time changes occur.
Timing is business-critical.
The more time-sensitive the workflow, the more important timezone clarity becomes.
Detect issues in your n8n workflows
|
Definitions
Timezone: The regional time setting used to interpret dates and schedules.
Server default timezone: The timezone configured at the operating system level.
Disclaimer
This article highlights common patterns and risks seen in real-world n8n workflows. It’s meant to help you build more confidently and avoid surprises as your automation grows. Behavior can vary depending on your setup, version, and configuration.