Scheduled Tasks: Set It Once, Claude Handles the Rest

Configure recurring tasks in Cowork — daily briefings, weekly reports, automated file processing. Claude runs them on schedule while you focus on what matters.

Scheduled Tasks is the feature that turns Claude Cowork from a reactive assistant into a proactive one. Instead of manually starting every task, you define what should happen and when — and Claude executes it automatically on the schedule you set.

Quick-start: Scheduled Task prompt
Medium ComplexitySafety Verified
Create a scheduled task that runs every weekday at 8:00 AM:

Task: Morning Briefing
Schedule: Mon-Fri 08:00

Steps:
1. Scan ~/DailyBriefing/emails/ for unread messages
2. Categorize by urgency: Critical, Action Needed, FYI
3. Parse ~/DailyBriefing/calendar.ics for today's meetings
4. Summarize top 5 news articles from configured sources
5. Compile into a 1-page PDF
6. Save to ~/DailyBriefing/output/DailyBrief_[DATE].pdf
7. Send me a notification when done

If any step fails, log the error to ~/DailyBriefing/logs/ and continue with the remaining steps.

What Scheduled Tasks Does

Scheduled Tasks lets you define recurring Cowork jobs that run automatically, without you needing to open Claude Desktop and type a prompt each time. You set the trigger (time-based or event-based), define the task, and Claude handles execution.

Key Capabilities

  • Time-based triggers: Daily, weekly, monthly, or custom cron-style schedules
  • Event-based triggers: When a file is added to a folder, when an email arrives, when a webhook fires
  • Multi-step execution: Each scheduled task can include the full power of a Cowork session — file access, MCP connectors, Computer Use
  • Failure handling: Configure what happens when a step fails — retry, skip, notify, or stop
  • Output delivery: Results can be saved to a folder, emailed, sent to Slack, or posted via webhook

How to Set Up a Scheduled Task

Step 1: Define the Task

Write out what Claude should do, in plain English. Be specific about:

  • Input sources (which folders, files, or APIs to read)
  • Processing steps (what to analyze, transform, or generate)
  • Output format and destination (file name, location, format)
  • Error handling (what to do if something fails)

Step 2: Choose the Schedule

Pick a trigger type:

  • Daily: Runs at a specific time each day (e.g., 8:00 AM)
  • Weekly: Runs on specific days of the week (e.g., Mon, Wed, Fri)
  • Monthly: Runs on a specific day each month (e.g., 1st of the month)
  • Custom: Cron expression for advanced schedules
  • Event-based: Triggered by file changes, emails, or webhooks

Step 3: Configure Output Delivery

Decide where the results should go:

  • Save to a local folder
  • Send via email
  • Post to a Slack/Discord channel (via MCP)
  • Call a webhook

Step 4: Test Once Manually

Before scheduling, run the task manually to make sure it works. Check the output, fix any issues, then schedule it.

Common Scheduled Task Patterns

Daily Morning Briefing

Schedule: Mon-Fri 08:00
Task: Scan emails, calendar, and news. Compile a 1-page PDF briefing.
Output: ~/DailyBriefing/output/DailyBrief_[DATE].pdf

Weekly Expense Report

Schedule: Sun 18:00
Task: Scan ~/Receipts/ for the past week. Extract vendor, date, amount.
       Generate an Excel summary. Email to [email protected].
Output: ~/Reports/Weekly-Expenses-[WEEK].xlsx + email

Nightly Backup Verification

Schedule: Daily 23:00
Task: Check that ~/ImportantData/ has been backed up to ~/Backups/ today.
       Compare file counts and sizes. Alert if mismatch.
Output: ~/Logs/backup-verify-[DATE].log + Slack alert if failed

Monthly Report Generation

Schedule: 1st of month 09:00
Task: Read all meeting notes from ~/Meetings/[PREVIOUS_MONTH]/.
       Generate a monthly summary with key decisions and action items.
Output: ~/Reports/Monthly-Summary-[YEAR]-[MONTH].md

Best Practices

Start Simple

Begin with a single, low-risk scheduled task — like a daily file organization job. Once it runs reliably for a week, add more complex tasks.

Log Everything

Have Claude write a log file for each run. Include: start time, steps completed, files created, errors encountered, end time. This makes debugging much easier.

Use Idempotent Tasks

Design tasks so that running them twice produces the same result as running them once. For example, name output files by date so re-runs don't overwrite or duplicate.

Set Up Failure Notifications

Don't let a scheduled task fail silently. Configure a Slack or email alert for failures so you can investigate quickly.

Review Outputs Periodically

Even automated tasks need oversight. Skim the outputs once a week to catch quality drift or edge cases.

Limitations

  • Claude Desktop must be running: Scheduled tasks only execute while the Claude Desktop app is open. If your computer is asleep or the app is closed, the task will be skipped or queued.
  • Usage limits apply: Each scheduled task consumes your plan's usage allocation. Complex tasks running frequently can hit limits fast.
  • No guaranteed execution time: Tasks may start a few minutes after the scheduled time depending on system load.

Frequently Asked Questions

Do scheduled tasks run if my computer is off?

No. Claude Desktop must be open and your computer must be awake. If a scheduled time is missed, the task is skipped (not run retroactively).

Can I have multiple scheduled tasks?

Yes. You can schedule as many tasks as your usage allocation supports. Most users run 3-5 recurring tasks.

How much usage does a scheduled task consume?

It depends on the task complexity. A simple file organization task might use a few minutes of allocation. A multi-step research briefing could use 15-30 minutes. Monitor your usage in Settings → Usage.

Can I pause a scheduled task?

Yes. You can pause and resume scheduled tasks at any time from the Cowork interface.