Skip to main content
0 reactions

n8n Tutorial — Part 3: Run a Workflow on a Schedule

Card titled Run a Workflow on a Schedule, labelled n8n Tutorial Part 3, with a clock node linked to a table node and three notes: every day at 9:00, your time zone not New York, runs on its own once published.

A schedule is the simplest way to put n8n to work: pick a time, and the workflow runs on its own, every day, without you opening anything. Getting the time right depends on one setting that’s easy to miss, the time zone.

In this part you run a workflow on a schedule with n8n’s Schedule Trigger. You set a daily time, make the workflow follow your own time zone, test it, watch it run on its schedule, and learn the other schedule types: every few minutes, cron expressions for weekdays only, and what happens to runs n8n misses while it’s switched off.

This is Part 3 of the n8n Tutorial. The parts in Module B, Workflow Basics:

  • Part 3: Run a Workflow on a Schedule (you are here)
  • Part 4: Webhooks: Start a Workflow from Any App
  • Part 5: Forms: Collect Data with n8n Forms
  • Part 6: Credentials: Connect n8n to Your Apps
  • Part 7: Executions, Debugging and Pinned Data
  • Part 8: Organise Your Workflows
All parts of the n8n Tutorial

Module A: Start Here

Module B: Workflow Basics

Module C: Working with Data

  • Part 9: Items and JSON: How Data Moves in n8n
  • Part 10: Expressions: Use Data from Earlier Nodes
  • Part 11: Transform Data
  • Part 12: Filter and Compare Data
  • Part 13: Dates and Times
  • Part 14: Files: CSV, Excel and PDF
  • Part 15: Data Tables: Store Data Inside n8n

Module D: Flow Logic

  • Part 16: If and Switch: Make Decisions
  • Part 17: Merge: Combine Branches
  • Part 18: Loops and Batches
  • Part 19: Wait and Human Approval
  • Part 20: Sub-workflows
  • Part 21: Error Handling

Module E: Code and APIs

  • Part 22: HTTP Request: Call Any API
  • Part 23: The Code Node in JavaScript
  • Part 24: The Code Node in Python

Module F: AI with Claude

  • Part 25: Your First AI Agent
  • Part 26: Give Your Agent Tools
  • Part 27: Memory That Lasts
  • Part 28: Answer from Your Documents
  • Part 29: AI Chains: Summarize, Classify and Extract
  • Part 30: Human in the Loop and Guardrails
  • Part 31: MCP in n8n
  • Part 32: Evaluations: Test Your AI Workflows
  • Part 33: Free Local AI with the Self-Hosted AI Starter Kit
  • Part 34: An n8n Agent in Microsoft Teams

Module G: Connect Apps and Extend n8n

  • Part 35: Connect Popular Apps with OAuth2
  • Part 36: Community Nodes
  • Part 37: Build Your Own Node
  • Part 38: Programmatic Nodes and Publishing
  • Part 39: The n8n API and CLI
  • Part 40: Build Workflows in Code with the Workflow SDK

Module H: Self-Hosting for Production

  • Part 41: Configure n8n with Environment Variables
  • Part 42: Run n8n on PostgreSQL
  • Part 43: Queue Mode and Workers
  • Part 44: Task Runners and Security
  • Part 45: Back Up, Restore and Update n8n
  • Part 46: Logs, Metrics and Tracing
  • Part 47: Put n8n Online with HTTPS

Module I: Users and Administration

  • Part 48: Users, Roles and Two-Factor Authentication

Module J: n8n Cloud

  • Part 49: Start an n8n Cloud Free Trial
  • Part 50: AI Workflow Builder, Assistant and Gateway Credits

Module K: Wrap-up

  • Part 51: Final Project, Cheat Sheet and What to Learn Next

Cost: free. Everything here runs on your own n8n Community Edition.

Every screen and output on this page is real, run with n8n 2 in Docker on macOS.

Get the Source Code

Get the complete source code of Scheduled Daily Log for n8n on Dewiride Store → (opens in a new tab)
It’s the finished, tested version of this part’s Daily log, with catch-up after downtime, a one-click table setup and n8n in Docker.

What You’ll Build

A Daily log: a workflow that runs every day at 9:00 in your time zone and adds a row to a data table with the day and the time it ran. It’s the shape of every scheduled job, from a morning report to a nightly clean-up: a schedule starts it, and the next node does the work. You start from n8n running on your computer.

Prerequisites

Step 1: Create the Daily Log Table

Create a data table named Daily log with two columns: day of type string, and ranAt of type datetime. How to Create a Data Table in n8n shows each click.

The empty Daily log data table with the columns id, day (string) and ranAt (datetime).
The Daily log table, ready for rows.

Step 2: Add a Schedule Trigger

Click + at the top of the left sidebar, then New workflow, and name it Daily log. Click Add first step, then On a schedule.

The node opens on Trigger Interval: Days. Keep Days Between Triggers at 1, set Trigger at Hour to 9am and keep Trigger at Minute at 0. That reads: every day at 9:00.

The Schedule Trigger settings with Trigger Interval Days, Days Between Triggers 1, Trigger at Hour 9am and Trigger at Minute 0, under a note that the workflow runs on this schedule once published.
Every day at 9:00.

The yellow note is the rule to remember: a schedule only runs once the workflow is published.

Step 3: Set Your Time Zone

9:00 where? Click Execute step to test the trigger. It outputs the time it ran, split into handy fields. Here, in India at 11:30 in the morning, it said:

Output (the lines that matter)JSON
{
  "timestamp": "2026-11-21T01:00:36.141-05:00",
  "Readable time": "1:00:36 am",
  "Day of week": "Saturday",
  "Timezone": "America/New_York (UTC-05:00)"
}

That’s New York time. A self-hosted n8n uses America/New_York unless you set a time zone, as n8n’s Schedule Trigger docs (opens in a new tab) explain, so this workflow would run at 9:00 in New York.

Close the panel. Click ⋯ next to the workflow name, then Settings. Open Timezone, type your city, choose your time zone (here Asia/Kolkata) and click Save.

The workflow settings for Daily log with Timezone set to Asia/Kolkata, below Execution Logic and Error Workflow.
Settings, then Timezone.

Open the trigger and click Execute step again. Now the time matches the clock:

Output (the lines that matter)JSON
{
  "timestamp": "2026-11-21T11:32:38.658+05:30",
  "Readable time": "11:32:38 am",
  "Day of week": "Saturday",
  "Timezone": "Asia/Kolkata (UTC+05:30)"
}

Step 4: Save Each Run in the Table

Add a Data table node after the trigger, choose the Insert row action and pick Daily log as the data table. The two columns appear under Values to insert.

From the INPUT panel on the left, drag Day of week onto day, and timestamp onto ranAt. n8n turns each into an expression that reads the field from the trigger.

The Data table node set to Insert row into Daily log, with day mapped to the expression for Day of week and ranAt mapped to the expression for timestamp.
day and ranAt, mapped by dragging.

Click Execute step. Testing this step writes a real row, so the table now holds one test row. Close the panel: the workflow is a schedule followed by an insert.

The canvas with a Schedule Trigger node connected to an Insert row node, both with green ticks after a test.
A schedule, then an insert.

Advertisement

Step 5: Watch It Run on Schedule

You don’t have to wait until tomorrow to see it work. Set the time a few minutes ahead: here 11am and minute 39.

The Schedule Trigger settings changed to every day at 11am, minute 39, to see a scheduled run a few minutes later.
A time a few minutes ahead, for a test.

Publish the workflow, then wait for that minute and open the Executions tab. The scheduled run appears without anyone clicking anything. Here it started at 11:39:43, 43 seconds after the minute. Runs started by the schedule have no flask icon; the flask marks your manual test runs.

The Executions list with runs at 11:43:43 and 11:39:43 started by the schedule, and three earlier manual test runs marked with a flask icon.
Scheduled runs have no flask icon.

Open the Daily log table: each run added a row with the day and the time.

The Daily log table with three rows, all Saturday, with ranAt times 11:32:38, 11:39:43 and 11:43:43 India time.
One row per run.

Now set the trigger back to 9am and minute 0, and publish again. A published workflow takes the new time when you publish it: here, changing the time to 11:43 and publishing again produced the next run at 11:43:43, without unpublishing first.

Step 6: Other Schedules

Trigger Interval offers Seconds, Minutes, Hours, Days, Weeks, Months and Custom (Cron). To run every 15 minutes, choose Minutes and enter 15. Since n8n 2.45, Seconds and Minutes schedules count from the moment you publish rather than from the top of the clock, so the runs fall 15 minutes apart from that moment.

For schedules the other types can’t express, such as weekdays only, choose Custom (Cron) and type a cron expression. This one runs at 9:00 from Monday to Friday:

ExpressionPlain text
0 9 * * 1-5

Read it left to right: minute 0, hour 9, any day of the month (*), any month (*), and days of the week 1-5, Monday to Friday. n8n shows the order under the field.

The Schedule Trigger with Trigger Interval Custom (Cron) and the expression 0 9 * * 1-5, above the format hint listing second, minute, hour, day of month, month and day of week.
Weekdays at 9:00 with cron.

n8n’s cron examples (opens in a new tab) cover hourly ranges, monthly and quarterly runs. To run one workflow on two schedules, click Add Rule in the trigger.

Step 7: Decide What Happens to Missed Runs

n8n can only start a run while it’s running. If your computer is off at 9:00, that day’s run is missed. The trigger’s Settings tab decides what happens when n8n comes back: If Execution Is Missed is set to Don’t Run Missed Executions by default.

The Schedule Trigger Settings tab with If Execution Is Missed open, listing Run the Most Recent Missed Execution Per Rule, Run the Most Recent Missed Execution and Don’t Run Missed Executions.
What n8n does with missed runs.

For a daily job on a laptop, Run the Most Recent Missed Execution is usually what you want: when n8n starts again, it runs once to catch up, then carries on as scheduled. Like any change, it takes effect when you publish.

Clean Up

Unpublish the workflow so it stops running, then archive and delete it from its ⋯ menu. Delete the Daily log table from the Data tables tab, as the data table guide shows. Deleting either can’t be undone.

Common Mistakes

MistakeWhat happensDo this instead
Not publishing the workflowThe schedule never runs; only your manual tests doPublish it
Leaving the time zone at the default“9am” means 9:00 in New YorkSet Timezone in the workflow settings
Expecting “every 15 minutes” to run at :00, :15, :30 and :45Since n8n 2.45, the runs count from the moment you publishUse Custom (Cron) with */15 * * * * for clock times

Troubleshooting

ProblemCauseFix
The workflow runs at the wrong timen8n uses another time zoneSet the workflow’s time zone (Step 3); n8n’s common issues page (opens in a new tab) also shows the instance-wide GENERIC_TIMEZONE setting
No run at the scheduled timeThe workflow isn’t published, or n8n wasn’t runningPublish it, and choose a missed-run option (Step 7)

FAQ

How do I run a workflow every 5 minutes in n8n?

Choose Minutes as the Trigger Interval and enter 5, then publish. The runs are 5 minutes apart, counted from when you publish.

Why did my run start after the minute?

Both scheduled runs here started 43 seconds after the minute. That still counts as on schedule: a run only counts as missed once it’s more than a minute late, the default grace period in n8n’s scheduler docs (opens in a new tab).

Can I set one time zone for all my workflows?

Yes. On self-hosted n8n, the GENERIC_TIMEZONE setting sets the default for the whole instance (n8n’s time zone settings (opens in a new tab)). A workflow’s own Timezone setting overrides it.

Does the schedule run when my computer is off?

No. n8n has to be running at that time. What happens when it comes back depends on the trigger’s If Execution Is Missed setting (Step 7).

Conclusion

A schedule needs three things: the trigger’s time, the workflow’s time zone, and a published workflow. You built a Daily log that runs every day at 9:00 your time, proved it by watching a scheduled run, and saw the other options: intervals, cron for weekdays, and what to do about runs missed while n8n was off.

← Part 2: Build Your First n8n Workflow

Next: Part 4: Webhooks: Start a Workflow from Any App →

Additional Resources

n8n and other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with or endorsed by n8n GmbH.

0 comments