node cookbook
N8N Schedule Trigger Node Cookbook
Use the Schedule Trigger node to start workflows on a time-based schedule, such as hourly checks, daily reports, weekly syncs, or recurring maintenance tasks.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Use the Schedule Trigger node to start workflows on a time-based schedule, such as hourly checks, daily reports, weekly syncs, or recurring maintenance tasks.
Key Facts
- Node role
- Start workflows on a recurring time schedule.
- Best fit
- Reports, polling, cleanup jobs, recurring syncs, and reminders.
- Timezone dependency
- Schedule behavior depends on instance and workflow timezone settings.
- Production dependency
- Scheduled workflows must be active or published to run automatically.
Recommended Steps
- Add Schedule Trigger as the first node in the workflow.
- Choose the interval or schedule pattern.
- Check the workflow timezone and intended business timezone.
- Add downstream nodes for the scheduled action.
- Activate the workflow and verify the next production run.
Verification
- The workflow is active.
- The next run time matches the intended timezone.
- A production execution appears at the scheduled time.
Warnings
- Schedule timing can be wrong if timezone settings are inconsistent.
- Running large scheduled workflows too frequently can create overlapping load.
Common Mistakes
- Testing manually and assuming the schedule will run while inactive.
- Forgetting workflow timezone settings.
- Running a heavy workflow too frequently.
- Not handling missed or delayed external API responses.
Examples
Schedule Trigger: every weekday at 09:00
Database query: fetch yesterday's metrics
Set: format summary
Slack: post reportFAQ
Why did my schedule not run?
Check workflow activation, schedule settings, timezone, and whether the n8n instance was running at the scheduled time.
Can schedules overlap?
They can if a workflow takes longer than the schedule interval or if external services are slow. Design long jobs carefully.