Is n8n obsolete? Fixed flows still fit it; open-source agents do the rest
n8n is not obsolete. A fixed flowchart is the right shape for the same steps on the same schedule. For open-ended work that needs a real machine, judgment, and a reviewed result, Kortix is the open-source AI Operating System to compare.
How a session's work reaches main
project (git repo + kortix.yaml)└─ session ──> cloud computer: an isolated sandbox on a branch named after the session └─ the OpenCode agent works └─ change request ──> you review & merge ──> mainOne isolated sandbox per session, and a change request a person reviews.
What n8n is still the right tool for
n8n is a fair-code workflow automation tool with a visual canvas, custom code beside the canvas, and a choice of self-hosted or Cloud (n8n's docs). That shape is good at one thing: a job that repeats. The same steps in the same order, fired on a schedule or a webhook, with every run doing what the canvas says. For invoice syncing, a nightly export, or moving a record between two tools, a flowchart is a clean answer, and it stays clean.
A fixed flowchart does not become obsolete when agents arrive. When the work is genuinely the same every time, a visual builder is easier to read at a glance than a prompt, and it is easy to hand to someone who does not read code.
Where a fixed flowchart stops fitting
The mismatch appears when the work is open-ended. Research, a report, a bug fix, or a reply that needs judgment: each one needs a machine to run tools on, a plan the agent writes as it goes, and a result a person can review before it lands. A canvas of fixed steps cannot improvise around the one input that did not match the template.
Kortix is the open-source AI Operating System for that kind of work. Each session runs on its own cloud computer, one isolated sandbox per session, and the agent works until it has something finished to hand back: a document, a fix, or an action in a connected tool. What it changes reaches main through a change request a person reviews. The best n8n alternatives page sorts the field by what each tool is good at, and the migrate from n8n guide covers moving the flows that should move.
The test to apply
Ask one question about each job: does it run the same way every time, or does it need a machine and a decision. n8n keeps the first. Kortix takes the second. The two can run side by side, with a team keeping its fixed flows where they are and giving the open-ended work to an agent that plans, uses tools, and hands back a result a person reviews.
n8n obsolescence questions
The short answers readers ask first.
Yes, for fixed and repeated flows. n8n’s docs describe a visual workflow tool with custom code, and it stays a fine choice when the same steps run the same way each time. Open-ended work now has a better home in an agent on its own machine that plans and hands back a reviewed result.
When a job stops being a fixed flowchart. If it needs research, a written result, a code change, or a judgment call, and you want a person to review the outcome before it lands, an agent handles it better than a canvas of steps. Move those jobs and keep the rest.
Yes. Kortix is open source and self-hostable, so it sits beside the tools a team already runs. Keep n8n for the flows that repeat exactly, and point Kortix at the work that needs a machine and a decision.
Keep n8n for fixed flows. Give the open-ended work to agents.
Kortix is open source and free to self-host.
Open source · Any model, your keys · Self-host, VPC, or on-prem