Restless vs n8n.
n8n is brilliant at explicit, repeatable automation. Restless is for open-ended work where judgement matters. They're more complementary than competing.
People ask me about n8n a lot, usually as "can't I just do this in n8n?". Sometimes the answer is genuinely yes. n8n is one of the best automation tools out there, and if your problem is a workflow you can draw, it's probably the right tool.
The interesting question is what happens when you can't draw it.
What n8n is
n8n calls itself a platform for AI agents and workflow automation. You build workflows on a visual canvas, connecting triggers, apps and logic, and drop into JavaScript or Python with npm packages when you need custom code. It connects to a huge number of services and has thousands of workflow templates.
On the AI side, it has agent nodes that can use tools, attach memory and pick from OpenAI, Anthropic, Google and open-source models. Tool calls can pause for human approval. Executions keep a history and can be retried, and workflows can be shared across a team, with more team features depending on the edition.
You can self-host it with Docker or use n8n Cloud. It's "fair-code" under the Sustainable Use License, with a separate enterprise licence for extra features.
Where n8n is great
n8n is the better pick for:
- Repeatable processes you can describe step by step: when this happens, do that, then this.
- Gluing lots of apps and services together with very little code.
- Seeing the whole flow visually and knowing exactly what will run.
- Dropping an AI step into an otherwise predictable pipeline.
Where Restless is different
Restless is built for the work you can't draw in advance: research where the next step depends on what you find, a proposal that goes through three rounds of feedback, a game build that needs testing on real devices. The route changes as you go. What stays fixed is the outcome and who owns it.
- Outcomes, not flowcharts. Restless's work graph describes outcomes, owners and revisions. The lead decides the route as evidence comes in.
- People in the work. Teammates co-edit documents, comment on a passage and review the exact result, alongside the agents.
- A company computer. Agents have a persistent Linux machine with files, Git, a browser and a desktop, not just API calls between apps.
- Company identity and quality. Approved facts, voice and visual language travel with the work, and you set a quality standard per outcome.
- Decisions, not alerts. Routine work stays quiet. What reaches you is a prepared decision with the evidence attached.
Use them together
This is the one comparison where I'd say "probably both" with a straight face. Once Restless's agents work out a process that's going to repeat exactly, turning it into deterministic automation is the right move, and in Restless that lives in the company's own scripts and tools on its computer. If your team already runs on n8n, there's no reason those workflows can't keep doing their job next to an office of agents.
Honest trade-offs
n8n has a vastly bigger integration library, years of production use and a visual editor that Restless deliberately doesn't have. Restless is a development preview. If your problem is "connect app A to app B every time X happens", use n8n. Restless would be overkill.