Most N8N workflows are reactive. A webhook fires, a form is submitted, a record changes, and N8N responds. But a significant category of business automation is time-based: pull a report every morning, send a reminder every Friday, sync data every hour, clean up old records every Sunday night.
That is where the N8N Schedule Trigger comes in. It is the simplest trigger node in N8N and one of the most powerful when you understand what it can do. This tutorial covers everything you need to know to build reliable scheduled automations, from basic daily runs to precise cron expressions for complex timing logic.
If you are new to N8N, start with How to Build Your First N8N Workflow and come back here when you are ready to put your automations on autopilot.
What the N8N Schedule Trigger Does
The Schedule Trigger node sits at the start of any N8N workflow and fires based on time rather than an external event. When the workflow is active, N8N watches the clock and executes the workflow at exactly the intervals you define.
Schedule Trigger: An N8N trigger node that starts a workflow automatically at configured time intervals. It replaces manual runs, external cron jobs, and task schedulers for any automation that needs to happen on a recurring basis.
You add it the same way you add any trigger: create a new workflow, click the trigger placeholder, and search for "Schedule Trigger." From there you have three scheduling modes to choose from.
The Three Scheduling Modes
1. Interval Mode
Interval mode is the simplest option. You pick a unit of time (minutes, hours, days, weeks, months) and a count. N8N runs the workflow every X units from the time you activate it.
Examples:
- Every 15 minutes: unit = minutes, value = 15
- Every 2 hours: unit = hours, value = 2
- Every 3 days: unit = days, value = 3
Interval mode is good for data sync jobs, API polling, and any task where you want consistent spacing between runs but do not care exactly what time of day the run starts.
2. Trigger at a Specific Time
This mode lets you set a fixed time of day and the days of the week to run. You choose hour and minute from dropdowns, then check which days of the week should trigger the workflow.
Examples:
- Every weekday at 8:00 AM: time = 08:00, days = Mon-Fri
- Every Monday at 9:30 AM: time = 09:30, days = Monday only
- Every day at midnight: time = 00:00, all days selected
This mode covers the majority of business scheduling needs. Daily reports, weekly digests, end-of-day summaries, that sort of thing.
3. Custom Cron Expression
For anything more complex, you use a cron expression. N8N accepts standard 5-field cron syntax:
minute hour day-of-month month day-of-week
Each field accepts a number, a wildcard (*), a range (1-5), a list (1,3,5), or a step (*/4). Here are the most useful patterns:
| Cron Expression | When It Runs |
|---|---|
0 9 * * 1-5 |
9:00 AM every weekday (Mon-Fri) |
0 */4 * * * |
Every 4 hours (midnight, 4 AM, 8 AM, noon...) |
30 8 1 * * |
8:30 AM on the 1st of every month |
0 18 * * 5 |
6:00 PM every Friday |
*/15 * * * * |
Every 15 minutes |
0 0 * * 0 |
Midnight every Sunday |
0 9,13,17 * * 1-5 |
9 AM, 1 PM, and 5 PM on weekdays |
Use crontab.guru to verify any expression before pasting it into N8N. It shows you exactly when the next several runs will fire, which saves time debugging.
Timezone Configuration
By default, N8N uses the timezone of the server where it runs. If your server is in UTC but your business operates in Paris, your "9:00 AM" workflow actually fires at 11:00 AM local time (or 10:00 AM depending on daylight saving).
Fix this by setting the Timezone field in the Schedule Trigger node. Enter any IANA timezone string:
Europe/ParisAmerica/New_YorkAsia/SingaporeAustralia/Sydney
N8N will convert your schedule to UTC internally but display and trigger relative to the timezone you set. If you ever suspect timezone drift, add a DateTime node immediately after the trigger and log its output to confirm the actual execution time.
How to Test Scheduled Workflows
You do not need to wait for the next scheduled run to test your workflow. Click Test workflow in the editor and N8N executes the entire workflow immediately, using a simulated trigger event with a timestamp representing the current moment.
All downstream nodes run with real data. You will see actual API responses, database writes, and Slack messages (or whatever your workflow does). This is how you verify logic before going live.
Once testing passes, activate the workflow with the toggle in the top-right. Deactivated workflows ignore their schedule entirely, so always confirm the toggle is on.
Hosting Requirements for Reliable Scheduling
Scheduled triggers only fire when the N8N process is running. This is the most common source of confusion for new users.
If you run N8N on your laptop, close the laptop, and open it again the next day, any scheduled runs that would have fired overnight simply did not happen. N8N does not backfill missed executions.
For business-critical scheduled automations, host N8N on infrastructure that stays online:
- N8N Cloud: The managed option. No server maintenance, always on, and scheduling works out of the box.
- VPS (DigitalOcean, Hetzner, Linode): Self-host N8N with Docker on a server that never sleeps. A 2GB Hetzner CX22 instance running Docker is enough for most small business workloads and costs roughly €4/month.
- Railway or Render: Managed container hosting with persistent processes. Good middle ground if you want managed infrastructure without N8N Cloud pricing.
For a complete walkthrough of hosting options, see our guide on N8N automation services or the upcoming self-hosting tutorial.
Six Real Business Automations to Build with Schedule Trigger
Here is where the theory becomes practical. These are the scheduled N8N workflows we build most often for clients.
1. Daily Sales Report to Slack
Schedule: Every weekday at 8:00 AM (0 8 * * 1-5)
Workflow: Schedule Trigger → HTTP Request (pull yesterday's orders from Shopify or WooCommerce API) → Code node (calculate revenue, order count, average order value) → Slack node (post formatted summary to #sales channel)
The operations team sees yesterday's numbers before the morning standup. No one needs to log into the e-commerce dashboard. Takes about 20 minutes to build. We pair this with a custom HTTP Request node to pull data from APIs that do not have native N8N integrations.
2. Weekly Lead Follow-Up Reminder
Schedule: Every Monday at 9:00 AM (0 9 * * 1)
Workflow: Schedule Trigger → HubSpot node (get contacts with status "contacted" and last activity older than 7 days) → IF node (filter contacts with no response) → Gmail node (send personalized follow-up email) → HubSpot node (update contact last activity date)
Every prospect who has gone quiet for a week gets a polite nudge automatically. The sales rep only sees replies, not the task of remembering who to follow up with.
3. Inventory Alert for Low Stock
Schedule: Every day at 7:00 AM (0 7 * * *)
Workflow: Schedule Trigger → Shopify node (get all product variants) → IF node (filter variants where inventory quantity is below threshold) → Slack node (post list of low-stock SKUs with current quantities) → Google Sheets node (append to inventory log)
The purchasing team wakes up to a Slack message with exactly what needs to be reordered. No spreadsheet refreshing, no manual stock checks. We built this pattern for a BBQ equipment brand and it cut their stockout incidents by roughly 60% in the first quarter.
4. Automated Invoice Chasing
Schedule: Every weekday at 10:00 AM (0 10 * * 1-5)
Workflow: Schedule Trigger → Xero or QuickBooks node (get invoices with status "overdue") → IF node (filter invoices past due by more than 7 days) → Gmail node (send overdue notice to client) → Xero node (add note to invoice record)
Chasing invoices is one of the least enjoyable tasks in running a small business. This workflow handles it without anyone on the team having to remember who owes what. For context on the ROI of automating financial admin tasks, see our Le Marquier case study, where we cut administrative overhead by 80% across their operations.
5. Hourly Data Sync Between Systems
Schedule: Every hour (0 * * * *)
Workflow: Schedule Trigger → Source API HTTP Request (fetch new/updated records since last run) → IF node (filter only records with changes) → Destination node (Airtable, Google Sheets, or CRM) → write updated records
When you have two systems that do not natively sync, hourly polling keeps them within one hour of each other. This is how we connect tools that do not have native integrations. For deeper coverage of connecting external APIs, read our N8N Airtable Integration tutorial.
6. Sunday Night Database Cleanup
Schedule: Every Sunday at 11:00 PM (0 23 * * 0)
Workflow: Schedule Trigger → Database node (query records older than 90 days with status "archived") → IF node (confirm records qualify for deletion) → Database node (delete matched records) → Slack node (post confirmation with record count removed)
Data hygiene rarely gets done manually because it is never urgent. A weekly cleanup workflow keeps your databases lean without anyone having to schedule the task.
Common Mistakes with Scheduled Triggers
These are the errors that cause scheduled workflows to behave unpredictably:
- Leaving the workflow deactivated. The schedule only fires when the workflow is active. Check the toggle is green before assuming it will run.
- Not setting the timezone. If your server runs UTC and your business is in a different zone, every scheduled time will be offset. Always set the Timezone field explicitly.
- Running N8N on a machine that sleeps. Laptops, desktop computers, and development environments that shut down will miss scheduled runs. Use a server or cloud host for production workflows.
- No error notification. Scheduled workflows run unattended. If they fail, nobody knows. Always add an Error Trigger workflow (a separate workflow using the Error Trigger node) that sends a Slack or email alert when any workflow encounters an error. This is covered in detail in our N8N error handling guide.
- Not logging run history. N8N stores execution history, but it rolls off. For critical scheduled jobs, write a summary to Google Sheets or Airtable at the end of each run so you have a durable record.
Combining Schedule Trigger with Other Nodes
The Schedule Trigger is rarely the interesting part of the workflow. Its value is in what it kicks off. A few patterns worth knowing:
Schedule + Wait node: You can add a Wait node inside a scheduled workflow to pause execution for a fixed duration or until a specific time. This is useful for sending a notification, pausing for an hour, then sending a follow-up.
Schedule + SplitInBatches: When a scheduled job pulls hundreds or thousands of records, use the SplitInBatches node to process them in chunks. This prevents memory issues and rate limit errors on downstream APIs.
Multiple schedules for one workflow: You cannot add two Schedule Triggers to a single workflow. If you need a workflow to run on multiple unrelated schedules (every weekday at 8 AM and also every Saturday at noon), create two separate workflows that share logic via a sub-workflow call.
If you are not sure where scheduled automation fits in your overall business picture, our AI readiness assessment helps you map out which tasks are strong candidates for automation and what the time savings would realistically look like.
What Scheduled Automation Actually Changes for Small Businesses
The practical effect of scheduled N8N workflows is that recurring tasks stop requiring human attention. Reports get sent. Follow-ups go out. Databases stay clean. Alerts fire. All of it happens whether your team is in the office or not.
This compounds over time. A workflow that saves 30 minutes of manual work per day saves roughly 130 hours per year. For a team of three running five such workflows, that is 650 hours per year recovered from repetitive tasks and redirected to work that requires judgment.
To understand the financial return on that time, use our ROI calculator, which translates hours saved into dollar figures based on your team's cost.
If you want to see what this looks like in production, the Le Marquier case study documents how a specialty consumer brand achieved 98% AI handling rate on their customer interactions, with N8N automation handling the back-office coordination that made the whole system work.
Frequently Asked Questions
What is the N8N Schedule Trigger node?
The N8N Schedule Trigger node starts a workflow automatically at a time you configure. You can set it to run every X minutes or hours (interval mode), at a specific time every day, on certain days of the week, or using a custom cron expression for precise scheduling. It replaces the need for external cron jobs or task schedulers when your N8N instance is running.
How do I write a cron expression in N8N?
N8N uses standard 5-field cron syntax: minute hour day-of-month month day-of-week. For example, 0 9 * * 1-5 runs at 9:00 AM Monday through Friday. 0 */4 * * * runs every 4 hours. 30 8 1 * * runs at 8:30 AM on the first day of every month. Validate expressions at crontab.guru before pasting them into N8N.
Will N8N scheduled workflows run if my computer is off?
Only if your N8N instance is running on a server or cloud host that stays online. Scheduled triggers require the N8N process to be active. If you run N8N on your laptop and close it, scheduled workflows will not fire. For reliable scheduling, host N8N on a VPS, a cloud platform like Railway or Render, or use N8N Cloud.
How do I test a scheduled N8N workflow without waiting for the next run?
Click Test workflow in the N8N editor. This executes the entire workflow immediately using a simulated trigger event, so you can verify your logic without waiting for the scheduled time. The test run produces real output from all downstream nodes. Once testing is complete, activate the workflow using the toggle in the top-right corner to enable live scheduling.
What timezone does N8N use for scheduled triggers?
By default, N8N uses the timezone of the server where it is running. You can override this in the Schedule Trigger node by setting the Timezone field to any IANA timezone string, such as Europe/Paris or America/New_York. Always verify your server timezone with the Date/Time node if scheduled triggers appear to be firing at unexpected times.
Ready to Get Started?
Book a free 30-minute discovery call. We'll identify your biggest opportunities and show you exactly what AI automation can do for your business.
