n8n now has Agents. You describe what an agent should do, give it a model and the tools and workflows it can use, and it works out the steps itself. You can talk to it in Slack, run it on a schedule, or call it from any workflow, and it&
n8n now has Agents. You describe what an agent should do, give it a model and the tools and workflows it can use, and it works out the steps itself. You can talk to it in Slack, run it on a schedule, or call it from any workflow, and it&
In context
- Topic: Low-Code y No-Code — Plataformas de bajo código, su gobierno y su deuda técnica.
- Source: n8n Blog
- Published: 25/09/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
Everything that gets automated stops being visible. That is the benefit and also the risk: the work does itself until the day it stops doing itself, and by then the person who understood the manual process has left the company.
I judge these tools by what happens the day they fail. An automated flow that breaks silently is worse than no flow, because nobody finds out until the customer complains. The first thing I ask is not what it integrates with, but how it tells you when it could not.
What usually goes wrong
What breaks these projects most is turnover. The flow was built by somebody who has left, they wrote nothing down, and now nobody dares touch it because they do not know what depends on what. It keeps running on inertia until it fails, and that day everyone discovers it was critical.
What to watch
- Whether the automated process made sense before automating it or only survived out of habit.
- What happens when the system on the other side changes, because it will change without warning.
- Cost per run at real volume, which on these platforms scales fast and surprises people.
How I read this entry
I would use it to free up time, not to cut headcount. That is the difference between an automation the team helps improve and one the team quietly sabotages. The second is more common than the slides admit.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
