Skip to main content
0 reactions

How to Set the Time Zone in n8n

Card titled How to Set the Time Zone in n8n, labelled n8n Tutorial how-to, showing a clock and three time zones with their offsets: America/New_York −05:00, Asia/Kolkata +05:30 highlighted, and Europe/London +00:00.

n8n runs every schedule and reads every date in one time zone, and a self-hosted n8n starts out on New York time. This guide shows how to set the time zone in n8n: once for every workflow with the GENERIC_TIMEZONE setting, and for a single workflow in its settings.

The example is a two-step workflow named What time is it: a manual trigger and a Date & Time node that reads the current date and time. The time it shows ends with the time zone’s offset from UTC, so you can see at a glance which time zone n8n used.

Cost: free. Time zone settings are part of n8n’s free Community Edition.

Every command, screen and output on this page is real, run with n8n 2 in Docker on macOS.

Prerequisites

  • For Step 2, the folder you run n8n from with Docker Compose. With n8n’s one-line setup, that’s the folder you ran the setup in: it holds the n8n folder.

Step 1: See Which Time Zone n8n Uses

Click + at the top of the left sidebar, then New workflow, and name it What time is it. Click Add first step, then Trigger manually. Click the + on the right of the trigger, search for Date & Time and pick Get Current Date. Leave its settings as they are and click Execute step.

The Date & Time node set to Get Current Date with Include Current Time on, and its output showing currentDate 2026-11-21T06:08:04.744-05:00.
−05:00: n8n used New York time.

The time in currentDate ends with -05:00: n8n used New York time, five hours behind UTC. It was 4:38 pm in India when this ran, and n8n showed 6:08 am.

To see which time zone a workflow uses, close the panel, click ⋯ next to the workflow name, then Settings.

The menu under the three dots next to the workflow name What time is it, listing Rename, Duplicate, Export JSON, Import, Version history, Settings and Archive, beside the two-node workflow on the canvas.
Settings is in the menu next to the workflow name.

Timezone reads Default - America/New York: the workflow follows n8n’s default time zone, and the default is New York. Close the settings.

The Workflow settings dialog for What time is it, with Timezone showing Default - America/New York.
The workflow follows n8n’s default, New York.

Step 2: Set n8n’s Default Time Zone

n8n takes its default time zone from the GENERIC_TIMEZONE setting. With n8n’s one-line setup, n8n’s settings live in the .env file inside the n8n folder.

Open Terminal in the folder that holds the n8n folder and run these two commands, with your own time zone in place of Asia/Kolkata. The Timezone list in the workflow settings shows every name n8n knows, such as Europe/London or America/Chicago. Where a name shows a space, type an underscore: America/New York becomes America/New_York.

TerminalBash
echo "GENERIC_TIMEZONE=Asia/Kolkata" >> n8n/.env
echo "TZ=Asia/Kolkata" >> n8n/.env

Each command adds one line to the end of .env. GENERIC_TIMEZONE is the time zone n8n uses for schedules and dates. TZ sets the same time zone for the container’s system clock, which commands such as date read; n8n’s Docker guide sets both.

Docker reads .env only when it creates the n8n container, so start n8n again with the start command from How to Install n8n with Docker. Docker re-creates the containers whose settings changed, and your workflows stay.

TerminalBash
docker compose -f ./n8n/compose.yml up -d
OutputPlain text
[+] up 6/6
 ✔ Container n8n-runners-1          Running                                           0.0s
 ✔ Container n8n-searxng-1          Running                                           0.0s
 ✔ Container n8n-sandbox-api-1      Healthy                                           7.9s
 ✔ Container n8n-n8n-1              Started                                           7.8s
 ✔ Container n8n-sandbox-runner-1-1 Started                                           7.7s
 ✔ Container n8n-sandbox-certs-1    Exited                                            0.6s

Reload n8n in your browser and open the workflow’s Settings again. Timezone now reads Default - Asia/Kolkata.

The Workflow settings dialog for What time is it, with Timezone showing Default - Asia/Kolkata after n8n was started again with GENERIC_TIMEZONE set.
The default is now Asia/Kolkata.

Close the settings and click Execute at the bottom of the canvas, then open the Date & Time node. The time now ends with +05:30, India time.

The Date & Time node output showing currentDate 2026-11-21T16:40:11.400+05:30.
+05:30: India time.

Step 3: Give One Workflow Its Own Time Zone

A workflow can run on a different clock from the default, for example one that sends a daily report to a team in London. Open the workflow’s Settings, click Timezone, type London and pick Europe/London. Click Save: n8n says Workflow settings saved.

The Workflow settings dialog for What time is it, with Timezone set to Europe/London.
This workflow now runs on London time.

Click Execute again and open the Date & Time node. The time ends with +00:00, London time in November. Every other workflow still follows the default.

The Date & Time node output showing currentDate 2026-11-21T11:10:49.193+00:00.
+00:00: London time.

To put a workflow back on the default, pick the first entry in the Timezone list, Default - Asia/Kolkata here, and click Save.

Clean Up

Keep the time zone you set in Step 2: that’s the point of this guide. Delete the example workflow: click ⋯ next to its name, then Archive. n8n goes back to your list of workflows, which hides archived ones: click Filters, tick Show archived workflows, then click ⋯ on the workflow’s card and Delete.

Warning: deleting removes the workflow permanently.

Confirm with Yes, delete.

Common Mistakes

MistakeWhat happensDo this instead
Editing .env and stopping theren8n keeps its old time zone: Docker reads .env only when it creates the containerRun docker compose -f ./n8n/compose.yml up -d after the change
Typing a name with a space, such as America/New York, in .envThe list shows spaces, but the setting’s names use underscoresWrite America/New_York
Setting one workflow’s Timezone to change them allOnly that workflow changesSet the default with GENERIC_TIMEZONE (Step 2)

Troubleshooting

ProblemCauseFix
A schedule runs hours early or lateThe workflow runs on another time zone, often n8n’s default, New YorkCheck its Timezone (Step 1), then set the default (Step 2) or the workflow’s own (Step 3)
no such file or directory: n8n/.envTerminal isn’t in the folder that holds the n8n folderGo to the folder you installed n8n in, then run the commands again

FAQ

What is n8n’s default time zone?

On self-hosted n8n, America/New_York. n8n Cloud tries to detect the owner’s time zone at sign-up and falls back to GMT (n8n’s Schedule Trigger docs (opens in a new tab)).

Which time zone wins, the workflow’s or the default?

The workflow’s own Timezone, when it’s set. A workflow on Default follows n8n’s default time zone.

How do I set the time zone on n8n Cloud?

n8n Cloud has no .env file. n8n’s docs set its default in the Cloud console, under Instance settings › Runtime › Time zone (Set your timezone (opens in a new tab)). A workflow’s own Timezone is in its settings, as in Step 3.

Does the Date & Time node have its own time zone?

Yes: Get Current Date has a Timezone option. Left empty, as in this example, the node follows the workflow’s time zone, which is why it showed London time in Step 3.

Conclusion

Set your time zone once with GENERIC_TIMEZONE and TZ in n8n’s .env, then start n8n again: every workflow follows it. Give a workflow its own Timezone in its settings only when it has to run on another clock.

Additional Resources

n8n, Docker and other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with or endorsed by n8n GmbH or Docker, Inc.

0 comments