SAP put money into n8n this week at a $5.2 billion valuation, and by lunchtime my HN feed had turned into a wall of workflow diagrams. There’s a “what I learned building an n8n masterclass” post sitting near the top too. The tool is having a genuine moment, and it deserves it. n8n is a lovely piece of engineering for wiring APIs together without living inside a Python file.

But watching the celebration, I kept catching on the same thing. n8n is a server. And a server can only reach the parts of your life that expose a clean, authenticated door.

What a workflow engine actually reaches

Picture the anatomy of an n8n job. A trigger fires, a node calls an API with a stored token, the response gets shaped, another node posts it somewhere. Webhooks in, HTTP out. It’s fast, it’s reliable, and it’s completely blind to anything that doesn’t hand it credentials up front.

So the question that matters isn’t “can n8n automate my work.” It’s “how much of my work lives behind an official API.” And for a lot of us the honest answer is: less than we’d like. The invoice portal your biggest client uses has no API. The internal admin dashboard behind your company SSO has no API. Your Gmail has one, technically, but getting an n8n node to touch it means minting OAuth scopes and praying the token doesn’t rot in ninety days.

The SSO wall n8n walks up to and stops

Here’s the scene that made this concrete for me. A friend runs ops for a small agency, and half her day is inside a vendor dashboard reachable only through Okta. She logged in this morning, she’s logged in right now, that tab is warm and authenticated and sitting three tabs to the left of this one.

She wanted n8n to pull a weekly report out of it. It cannot. There’s no endpoint, the login is federated through her company identity provider, and the session that proves she’s allowed in exists only inside her Chrome, tied to cookies and a device check that a headless server two data centers away has no way of reproducing without basically committing to impersonating her. So the workflow that was supposed to save an hour a week got stuck at step one, and she went back to copy-pasting cells like it was 2014.

That gap is not a bug in n8n. It’s the shape of the whole category. Server-side orchestrators live in a world of tokens. A huge amount of real work lives in a world of sessions.

Where the already-authenticated tab wins

A browser agent starts from the opposite end. It doesn’t ask for a token because it doesn’t need one. It runs inside the Chrome you already opened, using the login state you already have, seeing the exact pixels you’d see if you did the task by hand.

That’s the whole pitch for something like dassi. It sits in the side panel, and when you point it at that Okta-gated dashboard, there’s no auth dance at all, because you’re the auth. The session cookie is right there. The device check already passed when you logged in this morning. Dassi just reads the page and does the thing.

I wrote more about why cloud-hosted agents choke on exactly this in an earlier post on tabs, and the argument is the same one that applies to n8n: if your automation runs somewhere other than your browser, it inherits your browser’s credentials only through fragile, expiring plumbing.

Two tools, two jobs

I’m not here to dunk on a $5.2 billion company. If your workflow is Stripe fires a webhook, enrich the customer, drop a row in Postgres, then n8n is the right answer and a browser agent would be a clumsy one. Use the API when there’s an API. That’s just correct.

The mistake is assuming the API-shaped world is the whole world. It isn’t. A big chunk of daily knowledge work happens on pages that were built for humans to look at, behind logins that were built for humans to hold. n8n can orchestrate the machines. It can’t sit in your chair.

And that’s the part the valuation headline quietly skips. The money says AI automation is huge, which is true. It doesn’t say the automation can reach the messy, authenticated, no-API corners where most of us actually lose our afternoons. For those, the tool has to run where you already are. Which, damn it, is a browser tab you’ve had open since breakfast.

So build the n8n masterclass. Wire up the webhooks. Then look at the eleven tabs you never automated because there was no door, and ask what could act inside them instead of knocking from outside.