Claude Code Routines: Automate Your Busywork (2026 Guide)
The little chores you do every day — summarizing the inbox, checking flight prices, chasing quiet clients — can just happen on their own. Here's how to build automations right inside Claude, no Make or n8n required.
Every week, you do the same little chores. Summarize the inbox. Check the flight prices before they jump. Tidy up the Downloads folder. Chase the client who went quiet. None of them are hard. They're just always there, and you always have to remember to do them.
So here's a better question: what if they just happened on their own — without you lifting a finger, or even being at your computer?
That's what Claude Code Routines do. You set an automation up once — what to do and when — and Claude runs it for you, over and over, on the schedule you picked. And if you've ever heard people rave about tools like Make or n8n and felt your eyes glaze over: good news. You don't need them. You build the automation by describing it in plain English.
So what's a routine, exactly?
A routine is an automation you set up once that Claude then runs on its own, on a schedule you choose. Instead of opening Claude every morning and asking it to do the same thing, you tell it once — "do this, every weekday at 8am" — and it just does it. It pulls in your files, connects to your apps, does the work, and hands you the result.
What you can actually automate
The fastest way to get it is to see it. Here's the kind of thing people put on autopilot.
Everyday life
- A summary of your inbox, waiting for you every morning.
- A flight-price watch that pings you only when the price actually drops.
- Your Downloads folder, tidied and sorted once a week.
- A daily roundup on a topic you care about — it watches the web and tells you what's new.
Customers & WhatsApp
- A short morning summary of your inbox, sent straight to your WhatsApp.
- Draft replies to your most common customer questions, ready for you to just hit send.
Marketing
- Watch your brand and your competitors daily — new posts, mentions, price changes — and get one tidy digest.
- Keep your content calendar from ever going empty: a fresh week of post ideas drafted every Monday.
- A weekly check on where you rank for the search terms that matter to you.
Sales
- A morning briefing: today's meetings, who to follow up with, and which deals are looking shaky.
- Auto-drafted follow-ups to leads who went quiet, so you just review and send.
- A weekly pipeline summary you never had to build yourself.
See the pattern? Anything boring, repeatable, and on a clock is a candidate.
The one decision to make first: local or cloud
Before you build one, there's a single fork in the road. Every routine is either local or cloud, and you choose each time.
- Local runs on your own computer. It can reach your files and every app you've connected, which makes it the right pick for most personal automations. The catch: Claude has to be open and your computer awake when it's time to run. Laptop asleep in your bag at 8am? It'll run the moment you open the lid.
- Cloud runs on Claude's own servers, so it fires even when your laptop is shut and you're on a beach. Two honest trade-offs: it uses more of your usage, and right now the cloud version is built more for developers (it works with code projects) and is still labeled "research preview." For everyday stuff, local is usually the sweet spot.
What you need before you start
- A paid Claude plan (Pro, Max, Team or Enterprise) — routines aren't on the free plan.
- The Claude Desktop app, fully updated.
- Any apps you want it to use (Gmail, Calendar, and so on) already connected.
How to set one up — two ways
The easy way: just ask Claude
In any Claude session, type /schedule and describe it in plain words:
/schedule every weekday at 8am, summarize my unread emails and send me the highlights
Claude asks a couple of quick questions, confirms the exact time, and saves it. That's the whole thing.
The clicky way: fill in the form
Prefer buttons? In the Claude Desktop app, open Routines (or Scheduled) in the sidebar, hit New, and choose Local or Cloud. Give it a name, write the instructions, pick how often it runs — hourly, daily, weekdays, weekly, or a one-off — and save.
Where to see everything you've built
As you add more, you'll want one place to see them all. You'll find your full list in the Claude Desktop app's Scheduled / Routines section, on the web at claude.ai/code/routines, or by typing /schedule list. From there you can pause one, run it right now, edit it, or delete it.
The pro tip that saves you later
This one's the difference between "set and forget" and "set and quietly break." Once you've got a handful of routines running, it gets genuinely hard to notice when one silently stops working.
So build the safety net right into the instructions. Add a line like this to every routine:
If anything goes wrong or you can't finish, email me a short note explaining what failed.
Here's why it matters: a routine can show a green "ran" checkmark even when it didn't actually do the job — a blocked website, a disconnected app. The green light only means it started, not that it succeeded. A self-reported heads-up email means you find out the moment something breaks, instead of a week later.
So… should you ditch Make and n8n?
Honest answer: not entirely. They're different tools for different jobs.
Make and n8n are brilliant at rigid, high-volume plumbing — move this exact data from here to there, a thousand times, the same way every time. Routines shine where judgment is needed: read this, figure out what actually matters, write a thoughtful reply, decide what's worth flagging. Most people use routines for the thinking work — and for everyday personal automation, routines on their own are plenty.
Now let's actually build one
Enough theory — let's do it together. Follow the hands-on guide and you'll have your first routine up and running in about five minutes.
One routine turns into ten
The moment your first automation runs while you're asleep, you're hooked — you stop doing busywork and start designing it away. Learning to build automations that actually save you hours (and knowing which tool to reach for) is exactly what we walk you through inside the club — no tech degree required.
Frequently asked questions
What's the difference between a routine and a scheduled task?
They're basically two names for the same idea: an automation that runs on a schedule. In practice, the local ones (on your computer) are often called scheduled tasks, and the cloud ones (on Claude's servers) are called routines. Either way, you set it once and it runs itself.
Do I need to know how to code?
For everyday local automations, no — you just describe what you want in plain English. The cloud version is currently more developer-oriented, but you can go a very long way without touching code.
How often can they run?
You choose: hourly, daily, weekdays, weekly, or a one-off at a specific time. There's a small daily cap on automatic runs (on lower plans it's only a handful a day), and every run uses your normal Claude usage — so save them for things that are genuinely worth it.
Will it run while my computer is off?
Only if it's a cloud routine. A local one needs your computer awake and the app open; if it missed its slot, it runs as soon as you're back.
Can it really replace Make or n8n?
For reasoning-heavy, personal automation, often yes. For rigid, high-volume data plumbing, those tools still win. Plenty of people happily use both — routines for the thinking, the others for the pipes.
Still have questions?
Stuck on a step, or want to send a screenshot and have someone take a look? That's exactly what the community is for — real people, quick answers, and no question too basic.
Try your first two weeks for $1No commitment · cancel anytime