Get AI income methods before they spread.
Free weekly intelligence newsletter.
Claude Routines run scheduled automations on Anthropic's cloud infrastructure using plain language instructions instead of drag-and-drop nodes. You write what you want the agent to do, set a schedule, and Anthropic runs it — no server, no n8n, no Make. The same output, at a fraction of the complexity.
What Is the Core Difference Between Claude Routines and n8n?
n8n workflows are built visually: you drag nodes onto a canvas, connect them, and configure each one through a UI. Claude Routines are written as natural language instructions — you describe the steps in plain English and Claude executes them on a schedule.
Where n8n requires you to understand each module's configuration options, a Routine requires you to describe what you want clearly. The tradeoff: Routines must be more precise than skills because there is no human to ask for clarification mid-run. Unattended execution means the instruction needs to be complete the first time.
Routines run on Anthropic's infrastructure — no self-hosted server, no VPS, no Docker container to maintain.
How Do You Build a Daily Mailbox Summary Routine?
The mailbox summary Routine runs every morning and produces a structured digest of your inbox. The instruction set covers four things: connect to Gmail, read emails from the past 24 hours, group them by sender and urgency, and write a summary to a Slack channel or a markdown file.
In n8n, this is four nodes with OAuth connections, error handlers, and formatting logic in each. As a Routine, it is a paragraph of plain text describing the same steps.
Nick built and ran this live during the demo. The Routine connected to Gmail via MCP, read the inbox, classified by urgency, and posted the summary to Slack — in one unattended run.
How Do You Migrate an Existing n8n Workflow to a Routine?
Export your n8n workflow as JSON. Open Claude Code and paste the JSON with the instruction: convert this to a Claude Routine. Claude reads the node structure, extracts the logic, and writes an equivalent Routine in plain language.
Nick demoed converting a transcript-to-proposal pipeline: n8n had seven nodes handling file input, Claude API call, formatting, and Google Docs output. The Routine version was six sentences.
Migrating one workflow takes under ten minutes — and the Routine is easier to update later because you edit plain text, not node configurations.
What Are the Limits of Claude Routines?
Routines work best for linear, well-defined tasks. If a workflow requires complex branching logic based on external conditions — for example, different actions depending on which of twenty possible API responses comes back — a Routine gets harder to write clearly. n8n handles that kind of branching through its router module.
Routines also require all connected services to be accessible via MCP or direct API. If a tool does not have an MCP connector and does not expose an API, the Routine cannot interact with it.
For most standard business automations — email summaries, data syncs, content pipelines, CRM updates — Routines cover the full use case cleanly.
What Does a Transcript-to-Proposal Pipeline Look Like as a Routine?
The pipeline takes a meeting transcript from Fireflies, reads the client requirements from the conversation, writes a structured proposal, and saves it to Google Docs. As a Routine:
- Fetch the latest transcript from Fireflies API
- Extract: client name, requirements discussed, timeline mentioned, budget signals
- Write a proposal with an executive summary, scope of work, timeline, and pricing
- Save to Google Docs via the Google Workspace MCP, in the client folder
Total instruction length: eight sentences. Equivalent n8n workflow: seven nodes, three OAuth connections, custom formatting code in a Function node.
Frequently Asked Questions
Do Claude Routines cost more than n8n?
Claude Routines consume Anthropic API credits based on the tokens used per run. n8n self-hosted is free to run but requires a server. n8n cloud has a monthly fee based on workflow executions. For most builders running a handful of automations daily, Routine costs are lower than n8n cloud and comparable to self-hosting once server costs are included.
Can a Routine connect to any API?
Any API that accepts standard HTTP requests. The Routine can include curl commands or Python scripts as steps. For services with official MCP connectors — Gmail, Slack, Google Drive, GitHub — the connection is even simpler.
How do you schedule a Routine?
Set a cron expression in the Routine configuration. Standard cron syntax applies: daily at 9am, every weekday at 8am, every hour. The minimum interval is currently one hour. The Routine fires on Anthropic's infrastructure at the scheduled time.
What happens if a Routine fails mid-run?
The run stops at the point of failure and logs the error. You can review the log and rerun the Routine from the beginning. For critical automations, build in explicit error checking steps — for example, verify the Gmail connection returned results before proceeding to the summary step.
Watch Nick build and migrate workflows live: Replace n8n With Claude Routines on YouTube
Get AI income methods before they spread.
Free weekly intelligence newsletter.
Automate Any Website With Claude Code + Playwright CLI