Claude+File Workflows
Claude and File Workflows: Scheduled Tasks, Triggers and Limits
How to turn on Claude's scheduled tasks in Cowork, what it can and cannot do, how to fix it when it stops working, and how to hand the whole job to The Drive AI from inside Claude.
The short answer
Claude automates recurring work through scheduled tasks in Cowork on Claude Desktop: describe a job and a cadence (hourly, daily, weekdays, weekly or on demand) and each run opens as its own Cowork session with your connectors, skills and plugins. It is a schedule, not a trigger: nothing runs because a file arrived. For a workflow that reads each new file and files it where it belongs, Claude hands the job to The Drive AI through its connector, you confirm the draft, and the workflow runs on every file from then on.
Set up
How to schedule a task in Claude on its own
Open Cowork on Claude Desktop
Scheduled tasks live in Cowork, which is available on paid plans (Pro, Max, Team, Enterprise). On Team and Enterprise an admin controls Cowork access, and on Enterprise an owner has to enable it first.
Scheduled, then New task
Click Scheduled in the sidebar, then New task. Choose Create with Claude, or Set up manually to enter a name, the prompt, an approval mode, the frequency, and optionally a model and a folder. Click Save.
Or ask for it in a conversation
Describe the task and how often it should run. Claude may ask a clarifying question, then shows the proposed name, schedule and instructions; click Schedule to create it.
Manage it from Scheduled
The Scheduled page lists upcoming and past runs. From there you edit the instructions or cadence, pause and resume, delete, or run a task on demand.
What it does
What Claude's scheduled tasks can and cannot do with files
It can
- Run a saved prompt hourly, daily, on weekdays, weekly, or only when you ask
- Use the same connectors, skills and installed plugins as any Cowork task
- Run remotely, so the schedule holds while the computer sleeps or the app is closed
- Work on files saved to your Claude account, and on local files when the task runs locally
- Open each run as its own session, so you can read what it did
It cannot
- Start because a file arrived: there is no trigger on an upload, an email attachment or a shared file, only a clock
- Keep a standing rule such as "read each new PDF and file it by vendor"; every run is a fresh prompt over whatever is there
- Run on the Free plan
- Run more often than the presets allow, which start at hourly
- Undo a batch of file changes as one action
Troubleshooting
Claude scheduled task not working?
Scheduled is not in the Cowork sidebar
Scheduled tasks need a paid plan. On Team and Enterprise, an admin has to allow Cowork for your account, and on Enterprise an owner enables it for the organization first.
A run was skipped
Tasks run remotely by default and keep their schedule. A task that needs local files or local apps runs only on your computer, so it needs the machine awake and the app open at the scheduled time.
The task ran but did nothing to my files
A scheduled task is a prompt. If it names a connector, that connector must be enabled for the task; if the files only exist on your computer, the task has to run locally. A job that should react to each new file is a workflow, not a schedule.
I want it to run when a file lands, not every morning
Claude has no file trigger. Ask The Drive AI from Claude (with its connector added) to set up a workflow: it watches an upload folder, an inbox, a channel or a drive, reads each file as it arrives, and files it by the rule you gave once.
Bigger jobs
Where it stops, and what The Drive AI adds
A scheduled task runs a prompt on a clock. The job most people mean by automating files, read each one as it arrives and put it where it belongs, is a trigger plus a standing instruction, which is what a workflow is.
| Job | Claude on its own | With The Drive AI |
|---|---|---|
| Start when a file arrives | Not possible. Runs on a schedule only. | Triggers on an upload, an email attachment, a shared file in Slack or Teams, a new file in a drive, or a schedule. |
| Decide where each file goes from what it says | A prompt per run, over whatever files are there. | The workflow reads each file (Ask AI About the File, Read Details from File) and moves or renames it by the rule. |
| Ask a person before acting | An approval mode per task. | Ask a Person to Approve shows the plan for that file; approvals expire after a set time. |
| Runs on a free plan | No. Paid plans only. | Yes, on files uploaded to The Drive AI. Connected inboxes and drives come with Max and Team. |
| See what happened to each file | Open the run's session. | Every run is recorded per file, can be replayed, and a failed run retries from the step that failed. |
| Test it before trusting it | Run now, then read the session. | Run an email workflow over past mail on the first few attachments, then switch it on. |
Add The Drive AI to Claude
Workflows on files uploaded to The Drive AI run on every plan, free included; connecting Gmail, Outlook, Slack, Teams or a drive comes with Max and Team. Workspace admins save workflows, which in a personal workspace is you.
Claude.ai and Claude Desktop
Open The Drive AI in Claude's connector directory, choose Connect and sign in. Connectors are on your account, so the desktop app gets it too.
Claude Code
claude mcp add --scope local --transport http thedriveai https://mcp.thedrive.ai/mcp
Server URL
https://mcp.thedrive.ai/mcp
Try it
Prompts for File Workflows
Set up a workflow: whenever a PDF is uploaded to this workspace, read it, rename it by vendor and date, and file it under Finance by month. Show me the draft before you save it.
The agent drafts the workflow with the product's own builder; nothing is saved until you confirm.
Every Monday at 8am, collect last week's invoices from this workspace into one folder named by the week and tell me the total. Draft it first.
A schedule is one of the triggers, so the weekly job Claude would run as a task runs here with the file steps built in.
Show me which workflow runs are waiting for someone's approval, and what each one wants to do.
Approvals are visible from Claude too, so a waiting run does not sit unseen.
FAQ
Common questions
Checked against the publishers' documentation and The Drive AI agent's own tool liston 2026-10-28. Sources:
Can Claude automate file organization?
Partly. Scheduled tasks in Cowork run a prompt on a cadence, and Anthropic lists file organization among the uses. Claude cannot react to a file arriving, and each run starts from a fresh prompt. For a standing rule that fires on every new file, Claude hands the job to The Drive AI through its connector.
Does Claude have scheduled tasks?
Yes, in Cowork on Claude Desktop, on paid plans. You create them from the Scheduled page or by describing the job in a conversation, and they run remotely unless they need local files.
Can Claude run something when a new email attachment arrives?
Not on its own. Through The Drive AI, a workflow watches Gmail or Outlook and handles every attachment as it arrives: saved, renamed from its contents and filed in the drive you choose. Connecting mail comes with Max and Team.
How do I run a Drive AI workflow from Claude?
Add The Drive AI from Claude's connector directory, then describe the workflow in plain words. The agent drafts it the way the Save button would check it, shows you the triggers and steps, and saves it once you confirm. Pause, edit and approvals work from Claude too.
Does a Drive AI workflow need a paid plan?
On files uploaded to The Drive AI it runs on every plan, free included. Connecting an inbox, a channel or a drive comes with Max or any Team plan.
Say it once, in the assistant you already use.
Ask The Drive AI directly, or add it to Claude and ask there. Either way the draft comes back for you to confirm before anything is saved or sent.
