SAP just led a round that values n8n at $5.2 billion. I saw the headline Tuesday morning and my first reaction wasn’t about the money. It was about how many API keys are buried inside that number.

n8n is workflow automation done well. You drag nodes onto a canvas, wire them together, and each node talks to some service through its API. Slack, Google Sheets, HubSpot, Postgres, Notion, whatever you’ve got. The product is genuinely good, and the valuation tells you the market for stitching SaaS tools together is gigantic. People want their software to talk to their other software without a human copy-pasting in the middle.

But every one of those nodes carries a cost almost nobody puts on the slide.

The credential you forgot you granted

Each node has to authenticate before it can do anything. So you generate an API key in one dashboard, or you click through an OAuth consent screen that asks for read and write access to your entire mailbox, or you paste a webhook URL into two separate settings pages and hope they line up. Now multiply that by the dozen services a real workflow actually touches.

What you’ve built, without quite noticing, is a credential graveyard. Keys that never expire sitting in a config somewhere. OAuth grants that are three job-changes stale and still live. Tokens scoped far wider than the one tiny thing the flow needs them for, because the narrow scope was annoying to set up and the broad one just worked.

And you own all of it now. Rotation, revocation, the security review when someone asks which third parties can read your CRM.

What a browser agent doesn’t have to do

Here’s the part that flipped my thinking. You are already logged into Slack. You’re already logged into Gmail, into HubSpot, into the admin panel for whatever internal tool your team built five years ago that has no API at all. Your browser is holding live, authenticated sessions to every service you use, right now, in tabs you have open.

A browser agent works inside those sessions. It doesn’t ask a service for programmatic access, because it isn’t a separate program knocking on the API door. It’s acting in the page you already opened, with the auth you already have, the same way you would if you were clicking. No connector to wire up. No token to rotate. No consent screen granting some startup permanent reach into your inbox.

This is why I keep telling people browser agents are the new API. The integration layer that n8n is so good at managing? A browser agent routes around it.

Two different bets

n8n bets that services expose clean APIs. Browser agents bet you’re logged in.

The thing the canvas can’t reach

Where this gap really shows is the long tail of software that has no decent API to connect to in the first place, which is most of the software inside most companies, and this is the genuinely underrated reason the browser approach matters more than it looks: the internal procurement portal, the legacy billing system, the state government website where you renew a license, the vendor dashboard that charges $100 a month extra just to enable CSV export, the HR tool nobody remembers buying. None of these will ever ship an n8n node. There’s no team building one and no business case to fund it. So in a node-based world, those tasks stay manual forever, because automation lives behind an integration that doesn’t exist. A browser agent doesn’t care whether the API exists. It reads the rendered page, fills the form, clicks the button, pulls the data, exactly as a person would, because rendering is the one interface every web app is guaranteed to have. That’s a damn big surface area to suddenly make automatable, and it’s the part the $5.2 billion valuation isn’t pricing in. We wrote up seven of these tasks that you’re probably still doing by hand right now.

The model is yours, the plumbing isn’t theirs

There’s a second thing n8n’s model quietly assumes, which is that your data and your credentials flow through their orchestration layer. With Dassi, the agent runs in your Chrome side panel and you bring your own LLM key, so the model talks to you and the page, and nobody runs a middleman server holding a pile of your tokens. BYOK isn’t a feature checkbox here. It’s the difference between renting an integration layer and not needing one.

I don’t think n8n is going anywhere. SAP didn’t write that check by accident, and for backend-to-backend pipelines with stable APIs, the node canvas is the right tool. But a lot of what people reach for n8n to do is really just clicking around inside tabs they already have open, with logins they already have. For that, the integration layer was never the point. It was the toll booth.

So before you build a flow with nine OAuth grants in it, open the tab and ask the thing in your side panel to just do it.