Skip to main content
0 reactions

Cron Expressions in n8n: Syntax and Examples

Card titled Cron Expressions in n8n, labelled n8n Tutorial how-to, showing the Custom (Cron) expression 0 17 * * * as five boxes labelled minute, hour, day, month and weekday, with the rows Every day at 5 pm, 17:00, and Ran Saturday 21 Nov, 17:00:00.

A cron expression packs a schedule into one short line: 0 17 * * * means every day at 5 pm. In n8n, you type one into the Schedule Trigger when its ready-made intervals can’t describe the schedule you need. This guide explains cron expressions in n8n field by field, runs a real one, and gives you tested examples to copy.

Cost: free. Schedules are part of n8n’s free Community Edition.

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

Syntax

A cron expression is five fields separated by spaces. n8n also accepts an optional sixth field in front of them, for seconds.

SyntaxPlain text
[<second>] <minute> <hour> <day-of-month> <month> <day-of-week>
  • <second> (optional): 0 to 59. Leave it out, and the schedule runs at second 0.
  • <minute>: 0 to 59.
  • <hour>: 0 to 23, on a 24-hour clock, so 17 is 5 pm.
  • <day-of-month>: 1 to 31.
  • <month>: 1 to 12, or the first three letters of the month’s name, such as jan.
  • <day-of-week>: 0 to 7, where 0 and 7 are both Sunday, or the first three letters of the day’s name, such as mon.

Each field takes a number, or one of these:

  • * means every value: * as the hour means every hour.
  • , makes a list: 1,15 as the day of the month means the 1st and the 15th.
  • - makes a range: 9-17 as the hour means 9 am to 5 pm, and mon-fri as the day of the week means Monday to Friday.
  • / makes a step: */15 as the minute means every 15 minutes.

The fields come from n8n’s Schedule Trigger docs (opens in a new tab); the ranges and names are those of cron (opens in a new tab), the library n8n reads the expression with.

Step 1: Add a Schedule Trigger with a Cron Expression

The example is a workflow named Every day at 5 pm with a single node: a Schedule Trigger whose cron expression runs it at 17:00 every day.

Click + at the top of the left sidebar, then New workflow, and name it Every day at 5 pm. Click Add first step, search for Schedule and pick Schedule Trigger. Open Trigger Interval and pick Custom (Cron).

The Schedule Trigger panel with the Trigger Interval list open, showing Seconds, Minutes, Hours, Days, Weeks, Months and Custom (Cron).
Custom (Cron) is the last interval in the list.

In Expression, type the cron expression:

ExpressionPlain text
0 17 * * *

Read it field by field: minute 0, hour 17, every day of the month, every month, every day of the week. Under the box, n8n shows the format it expects.

The Schedule Trigger panel with Trigger Interval set to Custom (Cron), Expression set to 0 17 * * *, and the hint Format: ([Second]) [Minute] [Hour] [Day of Month] [Month] [Day of Week].
0 17 * * *: every day at 17:00.

The hour is in the workflow’s time zone. This n8n runs on India time; to set yours, see How to Set the Time Zone in n8n.

Step 2: Publish and See It Run

A schedule runs only once its workflow is published. Close the panel, click Publish, then Publish in the dialog (How to Publish a Workflow in n8n shows each screen).

At 17:00, the run shows up under the Executions tab above the canvas.

The Executions tab of the workflow Every day at 5 pm, showing a run on Nov 21 at 17:00:00 that succeeded in 121ms.
The schedule ran at 17:00:00 on its own.

Click the run to open it. The Schedule Trigger’s output says when it fired, in the workflow’s time zone.

The Schedule Trigger output in JSON, with timestamp 2026-11-21T17:00:00.000+05:30, Readable time 5:00:00 pm, Day of week Saturday, Hour 17, Minute 00 and Timezone Asia/Kolkata (UTC+05:30).
The run fired at 17:00, India time.

More Cron Expressions to Copy

ExpressionRuns
*/5 * * * *Every 5 minutes
0 * * * *Every hour, on the hour
0 9 * * *Every day at 9:00
30 8 * * 1-5Monday to Friday at 8:30
0 9 * * mon-friMonday to Friday at 9:00, with day names
0 12 * * 1Every Monday at 12:00
*/15 9-17 * * 1-5Every 15 minutes from 9:00 to 17:45, Monday to Friday
0 0 1 * *At midnight on the 1st of every month
0 0 1 1,4,7,10 *At midnight on the 1st of January, April, July and October
*/10 * * * * *Every 10 seconds (six fields: seconds first)

To change the schedule of a published workflow, paste the new expression and publish again: until you do, the published version keeps running on its old schedule.

Clean Up

The example runs every day at 17:00 until you stop it. Click the arrow next to Published, then Unpublish, and confirm with Unpublish. Then delete it: click ⋯ next to its name, then Archive. n8n goes back to your list of workflows, which hides archived ones: click Filters, tick Show archived workflows, then click ⋯ on the workflow’s card and Delete.

Warning: deleting removes the workflow permanently.

Confirm with Yes, delete.

Common Mistakes

MistakeWhat happensDo this instead
0 5 * * * for 5 pmIt runs at 5 am: hours use a 24-hour clock0 17 * * *
* 17 * * * for 5 pmIt runs every minute from 17:00 to 17:59Put 0 in the minute field: 0 17 * * *
Expecting your own time while n8n runs on another time zoneIt runs at 17:00 in that time zone, often New York, n8n’s defaultSet the time zone first (How to Set the Time Zone in n8n)

Troubleshooting

ProblemCauseFix
Problem in node ‘Schedule Trigger‘: Invalid cron expressionA field is missing or extra, or a value is out of range, such as minute 60 or hour 24Use five fields (six with seconds), each within the ranges under Syntax
No run at the time you setThe workflow isn’t publishedPublish it (Step 2)
The run comes hours early or lateThe workflow runs on another time zoneCheck its Timezone in the workflow settings

FAQ

Can a cron expression run every few seconds?

Yes: add the seconds field in front. */10 * * * * * runs every 10 seconds.

Is Sunday 0 or 7?

Both work: 0 9 * * 0 and 0 9 * * 7 each run on Sundays at 9:00. So does 0 9 * * sun.

Does a cron schedule count from when I publish?

No. The Seconds and Minutes intervals count from the moment you publish, but a cron expression keeps its own times (n8n’s docs (opens in a new tab)): 0 17 * * * runs at 17:00, whenever you published it.

What if n8n is off at the scheduled time?

By default, n8n skips the missed run and carries on with the schedule. To run it late instead, change If Execution Is Missed on the Schedule Trigger’s Settings tab.

Conclusion

A cron expression is five fields, minute, hour, day of the month, month and day of the week, with an optional seconds field in front. Type it into the Schedule Trigger’s Custom (Cron) interval, check the workflow’s time zone, and publish.

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