Routines, automate your workflows

Who it's for

Routines are for entrepreneurs, solobuilders, freelancers and consultants who have recurring tasks that eat time without adding cognitive value. Morning monitoring, inbox summary, prospect follow-ups, weekly reporting, internal dashboards. If you catch yourself doing the same 10 minutes of Ctrl+C / Ctrl+V every Monday, this is for you.

What you can do

The whole thing sits on three moving parts.

Schedule. You pick when Claude runs. Daily at 7am, weekly Friday afternoon, or on external trigger (an email arriving, a calendar date, a webhook).

Execute. Claude does the work. It reads the sources you gave it, produces the deliverable (summary, draft, report, todo list) and drops it where you actually work: Notion, Drive, an email waiting for you when you wake up, or a Slack message.

Combine with connectors. A single routine can chain multiple tools. Read Gmail, scan a Notion database, pull this week's Linear tickets, push the final result into a Slack channel. Configure once, it runs forever.

How much it costs

Routines are included in paid claude.ai plans (Pro and above). No per-execution billing as long as you stay within your usage limits.

When to use Routines vs other tools

Routines are for cross-surface recurring tasks without code. You want Claude to read your Gmail, summarize, write into Notion, done. No terminal, no repo.

Claude Code /loop is different: it's a local loop to iterate on build/test inside your project. It lives in your terminal, it doesn't persist, it's dev work.

The Agent SDK is for custom pipelines you own and host yourself. When Routines isn't enough, or when you want granular control over prompts, retries, logging.

Safety

The rule: Claude produces, you validate. Routines always drop into a private space (your Notion, your Drive, your email) before anything goes out to an external recipient. Automation without a guardrail isn't productivity, it's debt building up silently.