How to schedule workflows in n8n?

You schedule workflows in n8n by using the Cron Trigger node. This node lets you run a workflow on a repeating schedule — for example, every hour, every day at 09:00, every Monday, or even with a custom cron expression. You simply add the Cron Trigger as the first node, pick the schedule you want, activate the workflow, and n8n will run it automatically on that schedule.

 

How Scheduling Works in n8n

 

n8n doesn’t have a central “global scheduler.” Instead, each individual workflow can be scheduled by placing a Cron Trigger node at the start. A trigger node is what “wakes up” a workflow. The Cron Trigger runs based on time rules you configure, and every time it fires, it outputs a simple JSON item so the rest of the workflow can run normally.

Here’s how to think about it in plain terms: the workflow sleeps, the Cron Trigger wakes it up at the scheduled time, and the workflow starts from that node.

 

The Practical Way to Schedule a Workflow

 

• Add a Cron Trigger node as the first node in the workflow.
• Choose the schedule mode you need. n8n offers:
  • Every X (e.g., every 10 minutes)
  • Daily (e.g., every day at 07:30)
  • Weekly (e.g., every Monday at 08:00)
  • Monthly (e.g., on the 1st of each month at midnight)
  • Cron Expression (for advanced custom timing)
• Save and activate the workflow. Inactive workflows do not run — even if the Cron Trigger is configured.

 

Example of a Real Cron Expression

 

If you choose the custom cron mode, you can use real cron syntax. For example, this runs the workflow every day at 02:15:

15 2 * * *

This is standard cron syntax, and n8n follows the same rules: minute, hour, day of month, month, day of week.

 

Important Production Notes

 

• The workflow must be activated. Saving is not enough.
• The Cron Trigger does not “catch up” on missed runs. If your server is offline at the scheduled time, that run is simply skipped.
• Long-running executions are allowed. If your workflow takes 30 minutes to finish and your cron runs every 10 minutes, n8n will start multiple parallel runs unless you build controls (for example, a lock system using a database).
• Time zone matters. n8n uses the server’s timezone unless overridden in environment variables. If you deploy via Docker or Cloud, confirm what timezone your instance is using so your schedules fire when you expect.
• No overlap protection built-in. If your workflow must never run twice at the same time, you must design that in your logic (e.g., database lock, check-file, or a queue).

 

A Simple Workflow Example

 

Below is a minimal JSON payload the Cron Trigger emits when it runs. You don’t usually need to use it, but developers like to know what’s happening under the hood:

[
  {
    "json": {
      "trigger": "cron"
    }
  }
]

That’s what flows into your next node. It’s just a starter item; the real work is done by the nodes after it.

 

When to Avoid Using Cron in n8n

 

• If you need extremely high-precision timing (sub-minute), n8n is not the right tool — use something external.
• If you need guaranteed execution exactly once no matter what, consider external schedulers or queue-based systems.
• If you need thousands of scheduled tasks, centralizing scheduling outside n8n may scale better.

But for normal business automation — daily ETL tasks, hourly API syncs, regular reports — n8n’s Cron Trigger is reliable and production-ready.