RoutineOS next to fixed-flow tools
Looking for n8n alternatives or Zapier alternatives? Those tools run steps you wired up. A RoutineOS routine is a Claude agent on a schedule. It reads, makes the call, shows what it based it on and is built to wait for your yes before it sends anything.
A fixed flow, or a routine that judges
The docs describe fixed-flow tools such as Zapier and n8n, with an AI step added, as flows you build and maintain. You decide every branch in advance. A routine works the other way round: you describe the job once and Claude does the reading and sorting.
A fixed flow
- You wire the stepsTrigger, filter, action, action. You build it and you maintain it.
- Every branch is decided up frontIf a case you did not plan for turns up, the flow has no answer.
- You keep it currentWhen the job changes, you edit the flow.
A RoutineOS routine
- Claude reads and decidesIt runs on a schedule on Claude's own cloud and makes the judgment call.
- You decide what leaves the buildingA gate stops every send, post or delete until a named person approves. The first run is report-only.
- It proposes its own tuningIt suggests setting changes from what you keep and drop, with the decisions it came from. Nothing applies until you say yes.
n8n alternatives and Zapier alternatives, side by side
The left column is what RoutineOS does. The right column is how the RoutineOS docs describe a fixed-flow tool.
| Topic | RoutineOS | Fixed-flow tool, as the docs put it |
|---|---|---|
| Judgment | Claude reads the page or inbox and makes the call. Code applies the rules you can edit. | Fixed flows you build and maintain, with an AI step where you add one. |
| Learning | Proposes setting changes from what you keep, drop and reject. You accept or reject each one. | A flow you maintain yourself. |
The docs do not compare workspace, approvals, triggers, hosting or cost, so this page does not either. For those, read each tool's own pages.
When to keep n8n or Zapier
A routine is not the right tool for every job. Keep your flow where these apply.
- The job has no judgment in it. If every case follows a rule you can write down, a fixed flow does it and nothing is gained by asking Claude.
- It has to react faster than an hour. RoutineOS runs on Claude scheduled tasks, and the minimum interval is one hour. A webhook, form or chat trigger becomes a schedule when you convert it.
- You do not use Claude. A routine runs on a Claude plan. Without one there is nothing to run it on.
- You need a settled platform. Claude scheduled tasks are a research preview and may change. RoutineOS inherits that.
You can keep a flow for the plumbing and use a routine for the part that needs a decision. The Zapier page shows one way to connect the two.
Move a workflow across
Already built it? Do not start again. Claude can turn it into a routine and list everything it could not carry over.
n8n
Built. Run one command and get a routine pack plus a MIGRATION.md.
Zapier
Guided from your description of the Zap. There is no export parser.
Windmill and others
Windmill converts from OpenFlow JSON. Other tools are not built yet.
Try it on one job
Pick the job that needs a decision and see a report-only first run before anything is sent.