Put Your Business On Autopilot With Claude Scheduled Tasks

Ever added up how many hours a week you spend doing work you've already done? Replying to an email in the same way you have 100 times before, or moving files from one location to another.

As solopreneurs, the repetitive work piles up because it still has to get done, and we’re the only ones doing. When it follows the exact same steps every time, it feels annoying (even though the steps are necessary to keep things running smoothly.

AI scheduled tasks can handle that work in the background while you spend your time on the things that need your brain. Once you know what type of work makes for a good scheduled task, the setup only takes a few minutes.

What makes something a good scheduled task

Keep in mind, not everything should be automated. A scheduled task works when the process meets a few specific criteria.

Here's what to look for:

• It follows the same steps every time. While you can write instructions that can take a few different paths (if X happens, do Y, otherwise Z), there still needs to be a defined set of steps to follow.
• It uses the same tools. Claude connects to the same apps on every run, whether that's your email or your file storage.
• It produces the same type of output. You know what you're getting at the end, whether that's a draft or a saved file.
• It runs on a set schedule. Daily, weekly, monthly, or quarterly.
• It requires no human in the loop. There's no point in the process where you have to stop and make a judgment call.

Katie Parrott, AI Editorial Lead at Every, goes through a specific process to determine if something is worth automating. She writes:

A new automation has to run manually three times before I schedule it. Its output has to produce something I use with less than five minutes of review. Four unused runs of an automation trigger a decision to change or retire it.

4 parts of a scheduled task

Every scheduled task has the same components, and once you can name them, the setup stops feeling mysterious. Here's what goes into one.

Instructions

In Claude, a skill file is the set of step-by-step instructions that Claude follows. For an email task, the skill might say: check this inbox, figure out what's new, apply labels, and draft replies using my templates.

In another AI tool, you might write out a prompt or a series of instructions in a similar way and save them to that tool.

How to Create Claude Skills for Repeatable Processes

Create Claude Skills for repeatable processes.

Tinkering With IdeasAnna Burgess Yang

Reference files

These hold the information Claude needs to do the work well: your voice and tone guide, brand guidelines, templates, and examples of what good output looks like.

These files live outside the skill file*,* so more than one task can point to the same file. If you need to make a change, you update the reference file, and every skill picks up the change.

External tools (MCPs)

Model context protocol, or MCP, is the connection that plugs an outside app into an app like Claude or ChatGPT. You connect the app, and then your AI tool can read data from that app (and sometimes, even write back to the app).

Your file storage, your database, your email, your newsletter platform — if you use it day to day, there's a decent chance an MCP already exists for it.

The schedule

Skill + recurring date/time = scheduled task. Daily, weekly, monthly — whatever makes sense for how often the work actually comes up.

A lot of my scheduled tasks run weekly. They’ll run at 4:00 am, so that when I sit down at my desk to work that day, the results are already waiting for me.

Where to keep your reference files

Reference files need to live somewhere Claude can reach them and where you can update them easily. The right location depends on how hands-on you want Claude to be with your files.

• Google Drive. Claude can read your files but can't update them (at least, not at the time I’m writing this). You make the changes yourself, and Claude fetches the current version on the next run. Good if you want Claude not to modify your files.
• Markdown files stored locally. Claude can read and write these through CoWork, which is why you'll see people online with elaborate systems of local markdown files. It works, but you're tied to that computer, so making a change while you're away from that device isn't an option.
• Notion [affiliate link*] pages. This is my preference. Claude can read and write through the Notion MCP. Since it's cloud-based, I can tell Claude to update a reference file mid-conversation without switching apps. I had Claude migrate my old Google Drive and markdown files over to Notion.

The distinction: reference files are separate from skill files. Skill is a specific flow for Claude to file. Reference files might be used across multiple skills, such as your voice and tone guide. Other reference files might include brand guidelines, information about you and your business, or templates you want Claude to follow.

3 examples of scheduled tasks for a solo business

The criteria are much easier to apply when you can see them working. Here's what's running in my business right now, and which platform each one handles.

1. Social media post creation (weekly)

• Looks at my recent blog posts
• References my voice and tone guide and past examples
• Turns long-form content into short-form social posts and sends them to Buffer

2. YouTube descriptions (weekly)

• Checks a Google Drive folder for a new video file and transcript
• References an example description so the format stays consistent
• Writes an optimized description and saves it back to the same folder

3. Email inbox triage (daily)

• Connected to a Gmail account dedicated to website inquiries
• Categorizes each new message and applies a label
• Drafts a reply from my templates (it doesn't send — I review and edit first)

Tips for getting the most out of scheduled tasks

• Run every new scheduled task manually before you let it run on its own. You'll catch permission prompts and missing reference files before the task runs unattended and fails.
• Put error handling in the skill file itself. Add a final step like "if anything in this process failed, send me an email with what went wrong." Claude's native Gmail connector can draft but not send, so you'll want Zapier connected to Gmail for this step.
• Not all MCPs are available in the cloud. Some are only available via Claude’s CoWork desktop app. If you have to use CoWork, make sure your computer doesn’t go to sleep or your scheduled task may not run.
• Keep reference files separate from skill files. A voice and tone guide should be one file that multiple skills point to, so a single update flows to every task that uses it.

Building your first scheduled task

Start by looking at one boring thing you did last week and will do again next week. Write down the steps in order and which apps you touch along the way. That’s what you’ll need through the skill file.

Then go to Claude and repeat the process. Make sure Claude connects to your apps and follows your instructions. At the end, say, “Now package this as a skill.” Once you’ve done that, you can create the scheduled task to run the skill on a schedule.

Once you see that first output, you'll start noticing other work in your week that makes sense for a scheduled task. It’s nice to free up the brain space, because now you’ve reduced the amount of time spent to simply output review.

Want to see what automation actually looks like in a solo business?
Check out my free guide.

Download

FAQs