— Loading
Download a working automation JSON
Can AI answer engines cite your site?
Outreach scripts that get replies
Find the 3 workflows costing you sleep
200+ prompts, ready to ship
12-month posting plan in 60 sec
Brand voice doc in 4 steps
Runway / Pika / Sora / Veo formats
Pick a frequency, set the time, done. You get the standard 5-field cron string plus a ready-to-paste n8n Schedule Trigger config — and the one n8n scheduling gotcha that trips up minute-precision runs.
In plain English
Every day at 09:00.
Cron expression
0 9 * * *n8n Schedule Trigger config
{
"name": "Schedule Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"parameters": {
"rule": {
"interval": [
{
"field": "cronExpression",
"expression": "0 9 * * *"
}
]
}
}
}n8n gotcha
Gotcha: n8n's Schedule Trigger with field: "minutes" ignores triggerAtMinute entirely — it just fires every N minutes from activation time, not on a clean clock boundary. If you need a specific minute (daily/weekly/monthly at an exact time), use field: "hours"/"days"/"weeks"/"months" with triggerAtHour + triggerAtMinute instead, or paste the cronExpression interval above.
Native-fields equivalent (recommended over raw cron in the n8n UI)
{
"rule": {
"interval": [
{
"field": "days",
"daysInterval": 1,
"triggerAtHour": 9,
"triggerAtMinute": 0
}
]
}
}Why this tool exists
Cron syntax is simple once you know it and completely unmemorable if you touch it once a quarter. Five fields, wrong order, and your workflow fires at 3am instead of 9am — or worse, fires every minute because a wildcard landed somewhere it shouldn't have.
The bigger trap is specific to n8n: the Schedule Trigger node's "every N minutes" interval mode silently ignores the exact-minute setting. It just fires every N minutes from activation time, not on the clock. I lost an afternoon to that once. This tool bakes the fix — field: "hours" with explicit triggerAtHour / triggerAtMinute — directly into the generated config.
Pair it with the Webhook Payload Builder and the n8n Workflow Generator when you're scoping a scheduled automation end to end.
Waseem, building from Bali · info@skynetjoe.com
Quick answers
A 5-field string — minute, hour, day of month, month, day of week — that tells a scheduler exactly when to run something. "0 9 * * 1-5" means 9:00am every weekday. This tool builds that string from plain-English choices so you don't have to memorize field order.
n8n's Schedule Trigger node has a field: "minutes" interval mode that fires every N minutes from whenever the workflow activated — it does not respect triggerAtMinute, so you can't land on a clean clock boundary that way. For anything that needs an exact minute (a daily 9:00am run, a specific weekly slot), use field: "hours"/"days"/"weeks"/"months" with triggerAtHour + triggerAtMinute instead, or paste the cronExpression interval this tool generates.
The cron expression itself is a standard format — it works anywhere that accepts raw cron syntax, including crontab, GitHub Actions, and most schedulers. The node-config JSON is n8n-specific.
No. The schedule and expression are built entirely in your browser. Nothing is logged or stored.