n8n cron expressions go in the Schedule Trigger node's Custom (Cron) mode and use five fields, minute, hour, day of month, month and day of week, with an optional seconds field at the front. */15 * * * * fires every 15 minutes and 0 9 * * 1-5 fires on weekdays at 9:00. n8n reads them in the workflow's timezone, falling back to the instance timezone, and only runs them once the workflow is published. Below: every common schedule with its interval-mode equivalent, and the free n8n cron generator.
An n8n cron expression is a schedule written as five space-separated fields, minute, hour, day of month, month and day of week, typed into the Schedule Trigger node's Custom (Cron) mode. */15 * * * * runs every 15 minutes and 0 9 * * 1-5 runs on weekdays at 9:00, in the workflow's timezone. If you would rather not write one, the free n8n cron expression generator builds it and shows the next run times.
Checked on 13 and 14 October 2026 against n8n's Schedule Trigger docs, its timezone variables and the 3.0 breaking changes. The examples table extends the one in n8n's docs; the interval equivalents use the node's own field names.
- 1Add a Schedule Trigger as the first node
It replaces the old Cron and Interval nodes.
- 2Set Trigger Interval to Custom (Cron)
Or pick Minutes, Hours, Days, Weeks or Months if one fits.
- 3Paste the expression into Expression
For example 0 9 * * 1-5 for weekdays at 9:00.
- 4Set the workflow timezone
In the workflow settings, so 9 means 9 where you are.
- 5Publish the workflow
A schedule only runs in a published workflow.
How does scheduling work in n8n?
Through one node, the Schedule Trigger. Put it first in a workflow and n8n starts the run on the schedule instead of waiting for a webhook or an app event. The older Cron and Interval nodes do the same job and are on n8n's list of nodes removed in 3.0, so replace them with a Schedule Trigger before that upgrade.
The setting that matters is Trigger Interval. Six modes give you plain fields: Seconds, Minutes, Hours (plus Trigger at Minute), Days (plus Trigger at Hour and Minute), Weeks (plus Trigger on Weekdays) and Months (plus Trigger at Day of Month). The seventh, Custom (Cron), gives you an Expression field. You can add several trigger rules to one node, each with its own interval, which often beats writing one clever expression.
- Every N seconds, minutes, hours, days, weeks or months
- Plain fields anyone can read later
- Hard to get wrong
- A Months rule skips a month that lacks the chosen day
- Several rules can sit on one trigger
- Lists, ranges and steps in one line
- Business hours, twice a day, chosen months
- Easy to mistype, so check the next run times
- Timing fixed to the clock and calendar
- Five fields, or six with seconds
One change is on its way. n8n's docs say that from version 2.45.0 the Seconds and Minutes intervals run at even gaps counted from when the workflow is published, not on clock boundaries, and that Custom (Cron) timing does not change. On 15 October 2026 the newest stable release was 2.43.5 and the newest beta 2.44.1, so if a schedule must land on :00, :15, :30 and :45, write it as cron. New to n8n itself? Start with the n8n tutorial for beginners.
What is the cron expression format in n8n?
Five fields separated by spaces, with an optional sixth at the front for seconds. The docs give the full order as second, minute, hour, day of month, month and day of week, and note the node still runs if you leave the seconds field out.
| Field | Values | Example |
|---|---|---|
| Second (optional) | 0 to 59 | Only in a six-field expression, at the front |
| Minute | 0 to 59 | */15 is 0, 15, 30 and 45 |
| Hour | 0 to 23 | 9 is 9 AM, 17 is 5 PM |
| Day of month | 1 to 31 | 1 is the 1st |
| Month | 1 to 12 | 12 is December |
| Day of week | Sunday to Saturday, 0 to 6 | 1-5 is Monday to Friday |
Four characters do the work:
| Character | Means | Example |
|---|---|---|
| * | Every value | * in the hour field: every hour |
| , | A list | 9,17: at 9 and at 17 |
| - | A range | 1-5: Monday to Friday |
| / | A step | */6 in the hour field: 0, 6, 12, 18 |
Two habits save most debugging. Avoid restricting both day of month and day of week in one expression: classic cron treats that as either-or rather than both, and the result surprises people. And remember when the expression is read. The docs say variables in it are evaluated only when the workflow is published, so changing a variable later does nothing until you unpublish and publish again.
Why does my cron fire at the wrong hour?
Almost always the timezone. n8n reads every field in one timezone, and it picks that timezone in a fixed order.
- 01Workflow timezone
Set in the workflow settings. Used whenever it is set.
- 02Instance timezone
Self-hosted: the GENERIC_TIMEZONE variable. Cloud: set in the admin dashboard.
- 03The default
Self-hosted: America/New_York. Cloud: detected at sign-up, with GMT as the fallback.
On a self-hosted instance, set GENERIC_TIMEZONE in your Compose file next to TZ; our n8n self-hosting guide shows where.
Copy-paste examples for every common schedule
Each row gives the expression and, where one exists, the interval-mode setting that does the same job. Prefer the interval setting when there is one: it reads plainly to whoever inherits the workflow.
Quick reference table
| Schedule | Expression | Interval-mode equivalent |
|---|---|---|
| Every 30 seconds | */30 * * * * * | Seconds, 30 |
| Every 5 minutes | */5 * * * * | Minutes, 5 |
| Every 15 minutes | */15 * * * * | Minutes, 15 |
| Hourly on the hour | 0 * * * * | Hours, 1, at minute 0 |
| Hourly at half past | 30 * * * * | Hours, 1, at minute 30 |
| Every 6 hours | 0 */6 * * * | Hours, 6, at minute 0 |
| Daily at 6:00 | 0 6 * * * | Days, 1, 6am, minute 0 |
| Twice daily, 9:00 and 17:00 | 0 9,17 * * * | Two Days rules, or cron |
| Weekdays at 9:00 | 0 9 * * 1-5 | Weeks, 1, Monday to Friday, 9am |
| Hourly 9:00 to 17:00, weekdays | 0 9-17 * * 1-5 | Cron only |
| Mondays at noon | 0 12 * * 1 | Weeks, 1, Monday, 12pm |
| Monthly on the 1st, midnight | 0 0 1 * * | Months, 1, day 1, 12am |
| Quarterly, midnight on the 1st | 0 0 1 1,4,7,10 * | Cron only |
| 25 December at 9:00 | 0 9 25 12 * | Cron only |
Notes on a few rows. 0 */6 * * * counts from midnight, not from when you published, so it runs at 00:00, 06:00, 12:00 and 18:00. In the day-of-month field, */3 means the 1st, 4th, 7th and so on, restarting each month; the Days interval with 3 counts days instead. A yearly date such as 0 9 25 12 * fires every year, so unpublish the workflow if you wanted it once.
The $now helper and the other date expressions are in the n8n expressions cheat sheet.
Interval or cron: which should you pick?
Pick by the shape of the schedule, not by habit. A plain cadence (every N minutes, hours, days, weeks or months) belongs in an interval mode, where there is no syntax to break. Anything with a list or a range, such as weekday office hours or chosen months, needs Custom (Cron). Two different cadences, say 9:00 on weekdays and 12:00 on Saturdays, are easiest as two trigger rules on one node.
Scheduled workflows are also the ones most likely to fail with nobody watching. If a weekly report matters, give it an error workflow, as the n8n error handling guide shows, and read five ways n8n workflows fail silently for the runs that finish green and still do nothing. For a worked weekly job, the stale-deal report in our n8n CRM automation guide is a Monday schedule of exactly this kind.
Not firing? Check these in order
- The workflow is published, not only saved as a draft
- You published again after changing the trigger or a variable it uses
- The workflow timezone is set, and it is the zone you mean
- The expression has five fields, or six only if you meant seconds
- Day of month and day of week are not both restricted
- The schedule includes today: 1-5 never runs at the weekend
- The Executions list shows no run at the expected time (a trigger problem) or a failed one (a workflow problem)
- A self-hosted instance was running at that moment
On that last point: if the instance was down when a run was due, n8n's docs describe an If Execution Is Missed setting on the node, which can run the most recent missed execution, and a grace period in seconds. They tie both to a durable scheduler that is on by default from 2.45.0, so check your version before relying on it.
Skip the syntax: the free n8n cron generator
Pick a schedule in plain words and the n8n cron expression generator gives you the expression, the matching Schedule Trigger settings and the next three run times in your timezone. It runs in the browser with no sign-up. n8n's own docs point to crontab.guru for the same job.
For more workflows to put on a schedule, see 25 n8n workflow ideas and the AI automation library. If you would rather build your own AI product than schedule workflows for clients, AI SaaS Builder is our program on building one on Supabase, Next.js and the Claude API.
n8n cron expressions: FAQ
Why does my n8n cron expression not fire?
Check four things in order. The workflow is published, because a Schedule Trigger only runs in a published workflow. The workflow timezone is the one you expect. The expression has the number of fields you meant, since a stray sixth field shifts everything by one. And the schedule really includes today: 0 9 * * 1-5 never runs on a Saturday. Then open the Executions list.
What timezone does n8n use for cron expressions?
The workflow's timezone if one is set in its settings, otherwise the instance timezone. On a self-hosted instance that comes from the GENERIC_TIMEZONE variable, which defaults to America/New_York. On n8n Cloud it is detected from the owner's sign-up details, with GMT as the fallback. Set it on the workflow so a copied workflow keeps its local time.
How do I make n8n run every 15 minutes?
Use */15 * * * * in a Schedule Trigger set to Custom (Cron), which fires at 0, 15, 30 and 45 minutes past every hour. Or set Trigger Interval to Minutes and Minutes Between Triggers to 15. The n8n docs say that from version 2.45.0 the Minutes interval counts from when the workflow is published, so use cron if the clock position matters.
Does n8n use five or six cron fields?
Either. The n8n docs describe six fields, second, minute, hour, day of month, month and day of week, and say the seconds field is optional. A five-field expression therefore starts at the minute. */30 * * * * * runs every 30 seconds, while */30 * * * * runs every 30 minutes. Count the fields whenever a pasted expression behaves oddly.
Should I use an interval or a cron expression in n8n?
Use the interval modes whenever they describe the schedule, because they are plain fields that anyone can read. Switch to Custom (Cron) for lists and ranges the fields cannot express: twice a day at 9 and 17, hourly within business hours, or particular months. You can also add several trigger rules to one Schedule Trigger instead of writing a harder expression.
Can n8n run a workflow on the last day of the month?
Not with one setting. The n8n docs list no last-day cron syntax, and the Months interval skips a month that lacks the chosen day. The dependable pattern is a cron of 0 0 28-31 * * followed by an If node that continues only when tomorrow is the 1st, using the expression {{ $now.plus({ days: 1 }).day }} equals 1.