⏰ n8n Cron Expression Generator
Generate cron expressions for n8n, Make.com, and automation workflows. Visual builder with common presets.
Schedule Builder
Construct complex cron schedules easily.
Use * for every minute.
0 = Sunday, 6 = Saturday.
Expression Preview
Your generated cron string and meaning.
Quick Presets
How to Use the Cron Generator
- Use Presets: Click a preset for common schedules (every hour, daily, weekly).
- Or Build Custom: Enter values for minute, hour, day, month, and day of week.
- Use * for "every": * in the minute field means "every minute".
- Use */N for intervals: */5 in the minute field means "every 5 minutes".
- Generate: Click to see your cron expression and description.
- Copy to n8n: Paste the expression into your n8n Cron trigger node.
Format: minute (0-59) hour (0-23) day (1-31) month (1-12) weekday (0-6, 0=Sunday)
Mastering Cron for Automation
Cron expressions are the universal language of scheduled automation. Whether you're using n8n, Make.com, Zapier, or traditional Unix cron jobs, understanding this syntax unlocks powerful automation capabilities. A cron expression is five fields separated by spaces, each controlling when your automation runs.
The Five Fields
1) Minute (0-59): When in the hour to run. 2) Hour (0-23): What hour of the day (24-hour format). 3) Day of Month (1-31): Which day of the month. 4) Month (1-12): Which month. 5) Day of Week (0-6): Which day of the week, where 0 is Sunday. An asterisk (*) means "every" - so * in the minute field means "every minute".
Common Patterns
The most common pattern is */N which means "every N units". */5 in the minute field runs every 5 minutes. */2 in the hour field runs every 2 hours. You can also use ranges (1-5 means Monday through Friday) and lists (1,3,5 means Monday, Wednesday, Friday). Combining these creates powerful schedules: 0 9 * * 1-5 means "9 AM on weekdays".
n8n-Specific Tips
In n8n, cron triggers are perfect for scheduled data syncs, report generation, and periodic checks. Remember that n8n uses UTC timezone by default - if you want 9 AM in EST, use 14:00 UTC (9 AM + 5 hours). For workflows that need to run more frequently than once per minute, use the Interval trigger instead of Cron.
Testing Your Cron
Before deploying a cron schedule to production, test it. In n8n, you can manually trigger workflows to verify they work correctly. For complex schedules, use online cron calculators to see the next 10 execution times and confirm they match your expectations. A mistake in cron syntax can mean your automation never runs or runs too frequently.
Frequently Asked Questions
What is a cron expression?
A cron expression is a string of 5 fields (minute, hour, day, month, day of week) that defines when a scheduled task should run. For example, '0 9 * * 1' means 'every Monday at 9:00 AM'.
How do I use cron in n8n?
In n8n, add a 'Cron' trigger node to your workflow. Paste your cron expression in the 'Cron Expression' field. The workflow will execute automatically on your defined schedule.
What does */5 mean in cron?
*/5 means 'every 5 units'. In the minute field, */5 means 'every 5 minutes'. In the hour field, */5 means 'every 5 hours'. The * means 'every', and /5 means 'divided by 5'.
Can I run a cron job every 30 seconds?
Standard cron only supports minute-level granularity. For sub-minute scheduling, use n8n's 'Interval' trigger instead of 'Cron', or run a cron job every minute that executes your task twice with a 30-second sleep.
What's the difference between 0 0 * * * and * * * * *?
'0 0 * * *' runs once daily at midnight. '* * * * *' runs every minute. The first two fields are minute and hour - using * means 'every', while 0 means 'at zero'.