How to Use the Schedule Trigger Node

The Schedule Trigger node runs workflows on a clock. No manual execution, no waiting for webhooks

. Set it once, and n8n fires your workflow at exactly the times you specify.

This matters for professional services firms running digest emails, monitoring dashboards, backup routines, and compliance reports. You need workflows that execute at 6 AM before partners arrive, or midnight on the first of each month for billing cycles.

This guide covers every configuration option in the Schedule Trigger node, with exact settings for common firm workflows.

Add the Schedule Trigger node from the Triggers panel. You'll see five scheduling modes: Interval, Daily, Weekly, Monthly, and Cron.

Time Zone Selection

Set this first. The Schedule Trigger executes in the time zone you specify, not your server's time zone.

Click the Time Zone dropdown and select your primary office location. Use America/New_York for Eastern Time, America/Chicago for Central, Europe/London for GMT, Australia/Sydney for AEST.

If you operate across multiple offices, create separate workflows for each time zone. A 9 AM digest in New York needs different timing than a 9 AM digest in London.

Interval Mode

Use Interval for recurring tasks that run every X hours or minutes. Monitoring workflows, API polling, and status checks fit this pattern.

Configuration:

1. Select "Interval" from the Mode dropdown
2. Set the interval value (example: 2)
3. Choose the unit: Seconds, Minutes, Hours, or Days
4. Click "Execute Workflow"

Example - Monitor Slack Every 15 Minutes:

• Mode: Interval
• Value: 15
• Unit: Minutes
• Time Zone: America/New_York

This fires every 15 minutes starting from workflow activation. If you activate at 9:07 AM, it runs at 9:07, 9:22, 9:37, and so on.

Daily Mode

Daily mode executes once per day at a specific time. Use this for morning digests, end-of-day reports, and daily backups.

Configuration:

1. Select "Daily" from the Mode dropdown
2. Set the execution time in 24-hour format (example: 06:00 for 6 AM)
3. Verify the time zone matches your target office

Example - Morning Partner Digest:

• Mode: Daily
• Time: 06:00
• Time Zone: America/New_York

Workflow executes at 6:00 AM Eastern every day. The digest arrives before partners check email at 7 AM.

Weekly Mode

Weekly mode runs once per week on a specified day and time. Perfect for weekly status reports, Friday backups, and Monday planning emails.

Configuration:

1. Select "Weekly" from the Mode dropdown
2. Choose the day from the dropdown (Monday through Sunday)
3. Set the execution time in 24-hour format
4. Confirm time zone

Example - Friday Afternoon Timesheet Reminder:

• Mode: Weekly
• Day: Friday
• Time: 14:00
• Time Zone: America/Chicago

Fires every Friday at 2 PM Central, giving staff the afternoon to submit timesheets before the weekend.

Monthly Mode

Monthly mode executes on a specific day of each month. Use this for monthly billing runs, compliance reports, and recurring client deliverables.

Configuration:

1. Select "Monthly" from the Mode dropdown
2. Set the day of month (1-31)
3. Set the execution time
4. Verify time zone

Example - First-of-Month Billing Report:

• Mode: Monthly
• Day: 1
• Time: 00:30
• Time Zone: America/New_York

Runs at 12:30 AM on the first of every month. The billing report is ready when the accounting team arrives at 8 AM.

Important: If you set day 31 and the month has only 30 days, the workflow skips that month. Use day 1 or the last day of the previous month for critical monthly tasks.

Cron Mode

Cron expressions give you complete control over scheduling. Use this for complex patterns like "every weekday at 9 AM" or "first Monday of each month."

Configuration:

1. Select "Cron" from the Mode dropdown
2. Enter a valid cron expression
3. Verify time zone

Cron Expression Format:

* * * * *
│ │ │ │ │
│ │ │ │ └─ Day of week (0-6, Sunday = 0)
│ │ │ └─── Month (1-12)
│ │ └───── Day of month (1-31)
│ └─────── Hour (0-23)
└───────── Minute (0-59)

Common Cron Patterns:

Every weekday at 9 AM:

0 9 * * 1-5

Every Sunday at midnight:

0 0 * * 0

First day of every month at 6 AM:

0 6 1 * *

Every 6 hours:

0 */6 * * *

Last day of every month at 11 PM (requires workaround - run on day 28-31 with conditional logic):

0 23 28-31 * *

Test cron expressions at crontab.guru before deploying to production workflows.

Daily Client Activity Digest

Scenario: Send partners a 7 AM email summarizing yesterday's client interactions across Clio, HubSpot, and Slack.

Schedule Trigger Configuration:

• Mode: Daily
• Time: 06:45
• Time Zone: America/New_York

Workflow Steps:

1. Schedule Trigger fires at 6:45 AM
2. HTTP Request node queries Clio API

   API

   Click to read the full definition in our AI & Automation Glossary.

   for yesterday's time entries
3. HTTP Request node pulls HubSpot deals updated yesterday
4. HTTP Request node fetches Slack messages from client channels
5. Code node formats data into HTML email template
6. Gmail node sends digest to partners distribution list

Digest arrives at 7:00 AM. Partners review before client calls at 9 AM.

Weekly Utilization Report

Scenario: Every Monday at 8 AM, send practice group leaders a utilization report for the previous week.

Schedule Trigger Configuration:

• Mode: Weekly
• Day: Monday
• Time: 07:30
• Time Zone: America/Chicago

Workflow Steps:

1. Schedule Trigger fires Monday 7:30 AM Central
2. Harvest API

   API

   Click to read the full definition in our AI & Automation Glossary.

   node pulls time entries from previous Monday-Sunday
3. Code node calculates billable vs. non-billable hours by attorney
4. Code node identifies attorneys below 80% utilization threshold
5. Google Sheets node writes data to shared dashboard
6. Gmail node sends summary to practice group leaders

Leaders review utilization in Monday morning meetings at 9 AM.

Monthly Compliance Backup

Scenario: First of each month, export all matter documents to secure cloud storage for compliance retention.

Schedule Trigger Configuration:

• Mode: Monthly
• Day: 1
• Time: 02:00
• Time Zone: America/New_York

Workflow Steps:

1. Schedule Trigger fires at 2 AM on the first
2. Clio API

   API

   Click to read the full definition in our AI & Automation Glossary.

   node lists all matters modified in previous month
3. Loop over matters, downloading documents via Clio API

   API

   Click to read the full definition in our AI & Automation Glossary.
4. Compress node creates encrypted ZIP archive
5. AWS S3 node uploads archive to compliance bucket
6. Slack node posts confirmation to IT channel

Backup completes before business hours. IT verifies by 9 AM.

Hourly Dashboard Refresh

Scenario: Update a real-time revenue dashboard every hour during business hours (8 AM - 6 PM weekdays).

Schedule Trigger Configuration:

• Mode: Cron
• Expression: 0 8-18 * * 1-5
• Time Zone: America/New_York

Workflow Steps:

1. Schedule Trigger fires hourly 8 AM - 6 PM weekdays
2. QuickBooks API

   API

   Click to read the full definition in our AI & Automation Glossary.

   node pulls current month revenue
3. Clio API

   API

   Click to read the full definition in our AI & Automation Glossary.

   node gets outstanding AR balance
4. Code node calculates revenue vs. target
5. Google Sheets API

   API

   Click to read the full definition in our AI & Automation Glossary.

   updates dashboard cells
6. Conditional node checks if revenue below target
7. If true, Slack node alerts CFO

Dashboard stays current. CFO gets immediate alerts on revenue shortfalls.

Workflow doesn't execute at expected time: Check the time zone setting. If your server runs UTC but you set America/New_York, there's a 4-5 hour offset depending on daylight saving time.

Monthly workflow skipped a month: You set day 31 but the month had 30 days. Change to day 1 of the following month or use day 28 with conditional logic.

Cron expression fires too frequently: Verify your expression at crontab.guru. The pattern * * * * * fires every minute, not every hour.

Workflow executes twice: You have two active workflows with identical Schedule Triggers. Deactivate one or adjust the timing.

Daylight saving time causes one-hour shift: The Schedule Trigger respects DST in the selected time zone. If you need absolute UTC timing regardless of DST, set time zone to UTC and calculate offsets manually.

Set critical workflows to run outside business hours. A 2 AM backup won't interfere with staff productivity.

Build in buffer time. If you need a report by 9 AM, schedule the workflow for 6 AM. This gives you three hours to troubleshoot failures.

Use Cron for complex patterns. Don't chain multiple Daily triggers when a single Cron expression handles the logic.

Monitor execution history. Check the workflow executions panel weekly to catch silent failures.

Document time zones in workflow names. Name your workflow "Daily Digest - 6AM ET" not just "Daily Digest."

Test schedule changes in a duplicate workflow first. Activate the new schedule, verify execution, then update production.

The Schedule Trigger turns n8n into a reliable automation platform for time-critical firm operations. Set it correctly once, and your workflows execute exactly when your business needs them.