Keep your team ready for clock changes. This setup watches a list of time zones and sends a heads up the day before daylight saving time starts or ends. Alerts go to Slack and email so meetings and support hours can be adjusted in time.

A daily schedule runs the check. A Code node holds your time zone list. The flow calculates current time per zone, computes tomorrow, and then checks if the zone is in daylight saving time today and tomorrow. An If step compares the two states. When a change is coming, a Slack message posts to your chosen channel and an email is sent with the same message. You can also run it by hand with the manual trigger for quick tests.

Add your time zones using standard names like America/New_York and Europe/Warsaw. Pick the Slack channel and enter SMTP settings for your email provider. Expect fewer missed meetings and smoother handoffs across regions. This is ideal for remote teams, operations managers, and customer support leads who schedule across multiple time zones.

• Daily schedule trigger runs the check automatically, plus a manual trigger for quick testing
• Editable time zone list stored in a Code node for simple maintenance
• Per zone time calculation to get the current local time for each region
• Tomorrow date calculation to compare today and tomorrow states
• Daylight saving detection using simple true or false fields
• If logic sends alerts only when a change is coming
• Slack channel message with a clear reminder for the team
• Email sent through SMTP with a helpful subject and body

• Reduce manual checking from 30 minutes to 2 minutes per change
• Cut meeting mixups by 80 percent when clocks shift
• Connect Slack and email so teams see the same alert
• Handle dozens of time zones without extra effort
• Improve accuracy by using system time rules for DST

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Slack and SMTP. See the Tools Required section above for links to create accounts with these services.
3. Open the Code node named Timezones List and replace the sample items with your own time zones using standard names like America/New_York and Europe/Warsaw.
4. Connect Slack: double click the Slack node, open the Credential to connect with menu, click Create new credential, then follow the on screen steps to approve Slack OAuth2. Name the credential clearly, for example Slack DST Alerts.
5. Select the Slack channel in the node so messages post to the right team space. Save the node.
6. Connect email: double click the Email Send node, choose Create new credential, select SMTP, and enter your SMTP host, port, username, password, and from address. Enable TLS if your provider requires it.
7. Set the Schedule Trigger to run once per day at a steady time. Use UTC to keep timing consistent across regions.
8. Click Execute Workflow to run a manual test. If no zone changes tomorrow, you should see no Slack or email. To test the alert path, temporarily add a zone that you know will change soon or adjust the list to a region with an upcoming shift.
9. Verify delivery by checking the Slack channel and the inbox used in the Email Send node. If messages do not arrive, recheck the Slack channel selection and SMTP settings.
10. Troubleshoot common issues: use correct time zone names with slashes, confirm Slack OAuth permission was granted, ensure your SMTP port and TLS settings match your provider, and review n8n execution logs for any error messages.