Automation library · Alerts and monitoring

Daylight saving time notification for different timezones

Started by a clock, and works across Email and Slack. 9 steps, 1 branch: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 5Service 2

The steps in the order they run, from what starts it.

  1. 1When clicking ‘Test workflow’Manual triggerStarts it
  2. 2Schedule TriggerSchedule triggerStarts it
  3. 3Timezones ListCodeLogic
  4. 4Calculate Zone Date and TimeSetLogic
  5. 5Calculate Tomorrow's DateDate TimeLogic
  6. 6Check If Daylight Saving TimeSetLogic
  7. 7Check If Change TomorrowIfLogic
  8. 8Send Notification On Upcoming ChangeSlackService
  9. 9Send Email On Upcoming ChangeEmail SendService

How it's built

Starts on
A clock
Steps
9, with 1 branch
Size
Medium: a working afternoon
Connects to
Email, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Email and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.