Starting with n8n v2.36, you can now use supported AI models and tool services on select n8n Cloud plans without creating a provider account or generating an API key. Choose Gateway credits instead of adding a credential. Six model providers and five tool services work right out of the box.
Starting with n8n v2.36, you can now use supported AI models and tool services on select n8n Cloud plans without creating a provider account or generating an API key. Choose Gateway credits instead of adding a credential. Six model providers and five tool services work right out of the box.
In context
- Topic: Low-Code y No-Code — Plataformas de bajo código, su gobierno y su deuda técnica.
- Source: n8n Blog
- Published: 16/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
Low-code changed who is allowed to build, and that is the real story. When someone in operations can assemble their own flow without going through IT, the organisation gains speed and inherits a new problem: nobody knows how many of those flows exist or who depends on them.
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
The frequent mistake is automating the exception instead of the common case. A flow gets built full of conditions to cover the odd cases, and that complexity makes it impossible to maintain. Automating the first eighty per cent well and leaving the rest to a person is usually the better deal.
What to watch
- Cost per run at real volume, which on these platforms scales fast and surprises people.
- How the flow reports failure, and to whom: without that, the error gets discovered by the customer.
- How many flows already exist and who maintains them, which is where the invisible debt shows up.
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.
