Automate Daily Work with Claude Routines

Claude Routines let you automate parts of your work on Anthropic's servers instead of your own machine, which means the report still runs when your laptop is out of battery. In this walkthrough I show you where Routines live inside Claude Code, how they differ from scheduled tasks, how to create one from a template or a rough prompt, and the use cases where they shine or fall flat.

What you need

• The Claude Code desktop application. Routines are only available through it
• The connectors you already set up in your Claude desktop application; routines reuse them directly

1. Where to find Routines in Claude Code (0:09)

Open the Claude Code desktop application, click More, then select Routines. That is the whole path:

Claude Code > More > Routines

2. Routines vs scheduled tasks (0:26)

This distinction matters. Scheduled tasks run on Claude Cowork and automate things too, but they need your computer on. If an automation triggers at 3:00 a.m. and your laptop runs out of battery, it does not run. Claude Routines are different: they run on the cloud, on Anthropic's servers, so you no longer need to leave your computer on.

3. Cloud execution and daily limits (0:47)

The trade-off is volume. With routines you have a hard limit of somewhere between five and twenty-five runs each day, whereas scheduled tasks have no limit and can be triggered at will. So routines buy you reliability and freedom from your hardware, at the cost of a capped run count.

4. Templates and reporting use cases (1:08)

The Routines window gives you templates to start from: daily briefing, email triage, issue triage, and more. But routines can go far beyond that. They can be very detailed and complex: analyze your entire CRM, check whether the tasks on a to-do list for a given project have been done, and create reports from it. Routines are how you fill in the gaps on all the annoying reporting work you ever had to do.

5. Manual routine setup (1:58)

When you create a new routine you choose local or cloud. Local behaves just like a scheduled task; cloud is the one that matters here. The manual form asks for a name, the instructions (everything you want the routine to do), and a trigger. I walk through this screen so you understand every field, but in practice I highly recommend you do not build routines by hand. Talk with Claude to create them instead.

6. Schedule and API triggers (2:43)

There are two triggers you will actually use. A schedule runs the routine at a given time on a given day. The API trigger means you can run routines remotely: on Notion, for example, you can create a button on a database, and clicking that button starts the routine. Just remember the five to twenty-five daily cap. You cannot spam this at will.

7. Connectors and permissions (3:12)

Routines get access to all of the connectors you already have inside your Claude desktop application. There is nothing new to connect. If the connectors you need are already set up, you simply allow them in the routine and it is ready to go.

8. Create a routine with Claude Code (3:37)

Here is the way I actually build routines: interactively. I told Claude Code what I wanted in rough terms:

I want to automate a daily brief.

From that rough prompt, Claude Code fills in the name, writes out the instructions, and sets the repository. If you never know how to start, this is a good starting block. Mine was set to run at 9:00 a.m. Click Create, and the daily routine is ready and running on the cloud.

9. Run a cloud routine test (4:27)

Select your routine and click Run Now to test it. You will see that a routine is literally the same as a Claude conversation: it creates the task, sends the prompt to Claude on the cloud, and comes back with the report. Connect it to your email or Slack so the report lands where it matters. Then iterate: run a test, look at the result, and if you are not happy, modify the instructions.

10. Best business use cases (5:07)

My favorite use cases are around reporting and social media. If you connect your Claude to something like Higgsfield, you can automate the production of social media content for yourself. And if you are not doing content for your business right now, you are falling behind, because everyone needs that authority and notoriety level.

11. When not to use routines (5:43)

People say n8n is dead. It is not. Routines are quite bad for high volume work, so I only recommend them for things that are done in one shot: reports, analysis, and similar. If you need high volume automations that do not require any AI, routines are not for you. For everything else, they are a fantastic quality of life improvement for your business or personal use.

Pitfalls and tips

• Respect the daily cap of five to twenty-five cloud runs; design around it instead of fighting it.
• Do not hand-build routines through the manual form. Create them by talking with Claude Code, then refine after a test run.
• Keep scheduled tasks for unlimited, computer-on automations and routines for the ones that must survive your laptop being closed.

Where to go next

A perfect routine candidate is the daily creator tracking system from Build an X Parasite System with Claude Code. And if you want the OpenAI-side equivalent of scheduled automation, see Master Codex Desktop in 30 Minutes.