n8n released agents that work out the steps themselves, while workflows set how far they can reach

Anyone who has built an agent in n8n knows the picture: a chat trigger, a memory node, an AI Agent with a few tools attached and a workflow around it all to hold it together. It works. But you have been assembling your computer part by part.

n8n is now selling the pre-built computer. The agent comes with memory, sessions, channels, versions and approvals, and you write what it should do, as if writing a brief for a colleague.

The smartest part of the announcement

The note example. A support agent has to write a note into the CRM. Without a workflow in between, you would give it full write access and hope the instructions keep it to the notes field.

With a workflow, the agent never holds those rights at all. It holds a workflow that does one thing: adds a note. That is the right way to let a model near your real systems. Not to trust it, but to give it only as much as it needs.

A boring workflow is the best guard for a clever agent.

They say it plainly themselves: for anything sensitive, start where the damage is small - limited tools, a test channel and approval for every action that writes to a real system.

The old agents keep working and nothing moves. The new ones are tried on a task where every request is different, and that is where the difference shows fastest.

The visual is generated code-art, no third-party images.