Can Claude Code Run on a Schedule? Scheduled Tasks vs n8n

Description and use

Choosing the right scheduler for Claude Code tasks depends on frequency, need for judgment, and local file access. Use Claude cloud tasks for judgment-heavy jobs, and n8n for frequent, rule-based workflows with configurable missed execution handling and failure alerts.

Problem

Choosing the right scheduler for recurring Claude Code jobs and handling missed or failed runs.

Outcome

By matching job characteristics to scheduler strengths, teams can avoid missed runs, ensure appropriate alerting, and maintain reliable automation.

Workflow

• Identify job requirements (judgment vs fixed rules, frequency, local file access, maintenance responsibility).
• Check job frequency: if >1 hour, consider Claude cloud task; if <1 hour, prefer n8n or desktop task.
• Determine need for local files: use desktop task or host script if local access required.
• Choose tool: Claude scheduled task for judgment-heavy jobs; n8n for rule-based, high-frequency, or team-maintained workflows.
• Configure scheduler: set interval, enable catch-up or missed execution handling, add error triggers in n8n, or include guardrails in Claude prompts.
• Implement alerting: use n8n Error Trigger for failures; for Claude tasks, embed notification logic in prompt or post results to a monitored channel.
• Monitor run history: review transcripts for Claude tasks, check n8n execution logs for missed runs.
• Adjust as needed: switch scheduler or modify interval based on observed performance and reliability.

Evidence

Cloud scheduled tasks can start on an API call or a GitHub event, not only on a clock.

Source

The shortest interval for cloud scheduled tasks is 1 hour; desktop tasks and /loop can run every minute.

Source

n8n’s Schedule Trigger node has a setting for this. The default, "Don't Run Missed Executions", discards a missed run and resumes on schedule.

Source

A run scheduled exactly on the hour, like 9:00, can start several minutes late. Anthropic's tip is to pick a few minutes past, like 9:07.

Source

If the computer sleeps through the scheduled time, that run is skipped. When the app starts or the machine wakes, Desktop checks the last seven days and starts exactly one catch-up run for the most recently missed time.

Source