How to make my Scheduled Trigger run workflow at a moment of a specific Time Zone

Questions
,
1

Hi! I need launch my workflow every midnight EDT, but it offers me -4 EDT time zone. I also use dates of every launch in other nodes, so it wouldn’t work me to just calculate the EDT midnight according to the time zone my Scheduled Trigger is showing. Kindly advise where to change the setting or something. Thank you!

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

I found the setting in the workflow: (GMT-04:00) Atlantic Time - Halifax - guess it’s EDT, but still not sure if there is not difference in summer/winter period. Kindly advise. Thanks!

4

In the latest versions of the Schedule Trigger node, the cron rules respect the workflow 's timezone. If the workflow doesn’t define a timezone, the n8n instance timezone is used.
If you want to trigger something every midnight EDT, then just pick your local timezone or the New York timezone.

However I haven’t tested what happens when the time changes during DST.
So, to be on the safe side, you could set schedule a restart of the instance right after the clock changes, and everything should then work on the correct timezone as expected.

5

Thanks for your reply, @netroy ! Broke my brain tbh. So in the workflow settings I’ve set time zone as (GMT-5:00) Easter Time. It’s the same as EDT, right? Well maybe except summer/winter time, but it’s apparently not what I can additionally keep in mind at the moment. Kindly let me know if this is enough, or anything else needs to be adjusted? My n8n current version is Version 1.42.1…

6

In the new versions of n8n we have changed the display names to only show the location, and not the UTC or GMT offset, because it was confusing people (since those offsets were static values).
I recommend updating n8n because the new version also has updated DST and timezone data to automatically use the correct time based on the timezone name.

For Eastern Time, you can use America/New York as the timezone. It’s the same as EDT. And this will also automatically account for summer and winter time.

7

Sorry. not Easter Time)) Eastern Time)) Got it. I’m afraid it’s not so easy for me to update it in a way it’s installed and I’ll anyway need help from my web master, who isn’t available right now. But so far it’s ±correct, right?

8

Since the Eastern Timezone hasn’t changed anything recently, I think you should be fine on 1.42.1, but I’d still recommend upgrading to 1.51.1 because we did an overhaul of the Schedule Trigger node to iron out a couple of issues.

1 Like
9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.