SAP put money into n8n this week at a $5.2 billion valuation, and my feed filled up with n8n masterclass threads about an hour later. One HN post walked through building a “fully autonomous” lead-enrichment workflow. It was genuinely impressive engineering. It also took the author forty minutes before a single lead got enriched, because half of that time was spent wiring up credentials.

That gap is the thing nobody in the celebration posts wants to sit with.

The part of the demo they fast-forward through

Every n8n workflow is a chain of nodes, and every node that touches an external service needs to authenticate to that service. Gmail node? OAuth grant. Airtable node? Personal access token, scoped and pasted into a credential slot. Slack, HubSpot, Notion, your CRM, that one scraping API you signed up for at 2am. Each one is its own little bureaucratic errand, and you do them before the automation does anything at all.

So the workflow builder’s real skill, the one those masterclass videos are quietly teaching, is credential management. You’re not automating your work. You’re becoming the person who administrates the tokens that automate a slice of your work.

What the tokens actually cost you

Here’s a number that stuck with me. A mid-sized n8n instance I saw described on Reddit had thirty-something stored credentials, each with real scopes attached, sitting in a self-hosted database that the ops person admitted they’d never rotated. That is thirty standing grants to thirty services, any one of which becomes a skeleton key the moment that box gets popped or that env file leaks.

And the OAuth grants don’t expire when you stop paying attention to them. They sit there. A token you created to test a workflow in March is still valid in July, still scoped to read your whole inbox, still one misconfigured node away from doing something you didn’t intend. This is the API-auth tax, and it compounds quietly, the way the worst kinds of debt do.

The valuation makes this louder, not quieter. SAP betting nine figures signals that connector-based automation is the presumed default now, the thing serious companies standardize on, which means more people are about to spend more weekends assembling credential graphs they’ll forget about by autumn.

Your browser already did the auth

You logged into Gmail this morning. You’re logged into your CRM right now. Your bank, your project tracker, that internal admin panel with no public API whatsoever — all of them recognize you in the tab you already have open, because the session cookie is sitting right there doing its job.

A browser agent works inside that reality instead of rebuilding it. Dassi runs in your Chrome side panel and acts through the page you’re already authenticated to, so there’s no OAuth grant to create and no token to store, because the login already happened and the browser already holds it. It reads the same screen you read. It clicks the same buttons you’d click.

I wrote before that browser agents are the new API, and the n8n moment sharpens why. When there’s no connector node for a tool, n8n’s answer is an HTTP Request node where you hand-roll the auth yourself. A browser agent’s answer is: the tool already opened in a tab, so go use it.

Nodes versus the thing you were going to do anyway

n8n is legitimately great at one shape of problem: a high-volume pipeline that runs unattended a thousand times a day, where the upfront credential cost amortizes across all those runs. If you’re syncing records between two systems at scale, build the workflow. That’s the right tool and I won’t pretend otherwise.

But most of what people are actually trying to automate isn’t that. It’s “read these forty support tickets and draft replies.” It’s “pull the numbers off this dashboard into a sheet.” It’s the messy, once-or-twice-a-week browser chore that would take longer to build a node graph for than to just do by hand. For that whole category the connector overhead never pays itself back, and I’ve argued the same thing about MCP’s forty tools that still can’t fill out a form.

A $5.2 billion valuation is a bet that automation belongs in a server talking to APIs. Maybe for the pipeline stuff, sure. For the tab you already have open, the plumbing is a tax you were never obligated to pay. You can try the browser-native version and skip straight to the part where something gets done.

Anyway. I still have a March-vintage OAuth token to go revoke.