Scheduled Tasks in Claude Cowork: Automate Recurring Work Without Code
How to put routines on a schedule in Claude Cowork, what that looks like in practice, and where the limits are.
Orcha Team
April 15, 2026
The daily check on bank balances, the Friday review of open items, the monthly close prep – many routines in finance repeat on a fixed cadence. With Scheduled Tasks in Claude Cowork, these routines can be planned directly from your own workspace – no coding required.
What Scheduled Tasks are
A Scheduled Task is a saved AI agent process that runs automatically at a defined time – daily, weekly, or on custom intervals. Claude uses the same connectors you already work with interactively – OneDrive, SharePoint, Outlook, Teams, as well as Google Drive, Gmail, or Slack – and delivers the result as a message, document, or spreadsheet.
Technically, it is the same Cowork run as a manually started task. The difference: you describe the task once and set the schedule. Tasks run locally – Claude Desktop needs to be open. If your machine was off at the scheduled time, Cowork automatically catches up on the next launch.
Three examples from day-to-day finance
Weekly accruals check
Every Monday morning, Claude scans your Teams channels for decisions that may require accruals or provisions – new contracts, warranty claims, or open legal matters – and compiles a short summary.
Example prompt:
“Read the Teams channels ‘Finance’ and ‘Legal’ from the last 7 days. Collect any posts that point to new obligations, warranty cases, or open legal issues. Write a short list with context to my inbox.”
Friday: weekly update for leadership
Friday early afternoon, Claude summarizes the relevant finance channels in Teams – decisions, open questions, status changes – and saves the result as a draft.
Example prompt:
“Read the Teams channels ‘Finance’ and ‘Controlling’ from the last 5 days. Summarize decisions, open questions, and status updates into a weekly update. Save the result as a Word file in SharePoint under ‘Weekly Updates’.”
Monthly close checklist
On the first business day of the month, Claude creates the close checklist based on last month’s template and fills in the current owners. The list just needs a quick review instead of being rebuilt from scratch every time.
Example prompt:
“Copy the close checklist from the Word document ‘Close Checklist March’ in SharePoint, update the date to the current month, and fill in responsibilities from the Excel file ‘Team Overview’. Save as a new document in the ‘Month-End Close’ folder.”
Chaining tasks
It gets interesting when the output of one task becomes the input for the next. An example:
- 1 7:00 AM: Task A reads raw data from multiple sources and writes it into a structured Excel file on SharePoint.
- 2 7:30 AM: Task B reads the file, computes the KPIs, and flags outliers.
- 3 8:00 AM: Task C packages the result into a note for the leadership meeting.
The advantage over a single large task: each step produces a readable intermediate result. If the chain breaks at any point – say, because a source is empty – it is immediately clear where the issue is, and that step can be restarted individually.
History and skipped runs
You can find the status of your tasks in Claude Cowork under Tasks: which runs succeeded, which are in progress, and which were skipped. Each completed run creates a message in your inbox that you can open and follow up on like any other task.
The most common reason for a skipped run: Claude Desktop was closed at the scheduled time. Cowork automatically catches up on the next launch. To avoid this, schedule tasks for times when the app is typically open – e.g., 9:30 AM instead of 6:00 AM.
Limits
- Tasks only run while Claude Desktop is open. If a run is missed, Cowork catches up on the next launch.
- Each run consumes tokens. High-frequency tasks (e.g., every 15 minutes) add up, even if the input hasn’t changed.
- No dual-control principle. Payment runs, postings, and approval workflows have their own authorization logic in the ERP – Cowork does not replicate that.
- Execution is tied to the person who created the task – it runs with their permissions and their token budget.
In practice, this means: Scheduled Tasks work well for personal routines – summaries, overviews, drafts, checklists. Core transactional processes stay in the systems built for them. Cowork sits upstream and downstream: it prepares processes and follows up on their results.
Tip: Ask Claude what to automate
After a week of regular work with Cowork, you can ask Claude directly: “Which of my recurring tasks could be automated as a Scheduled Task?” Claude knows your conversation history and will suggest specifically what fits a schedule.
Setting up the task works the same way: describe what the task should do – Claude will help you create it, pick the right connectors, and set the schedule.
Sources
Anthropic Documentation
Related articles
More articles from our series on Claude for finance teams: From Chat to Autopilot | AI as a Coworker | Why Claude Cowork for Finance Teams
Want more guides like this?
Subscribe to our newsletter for new resources delivered straight to your inbox.