SAP just put a $5.2 billion valuation on n8n, the workflow automation startup the no-code crowd has been raving about for two years. The headline landed on a Tuesday, and by that afternoon half my feed was treating it as proof that cloud automation had finally grown up. But I read it the other way around.

Because n8n, for all its node-dragging elegance, runs on a promise you keep paying into. Every service you want it to touch needs a credential. A Google OAuth token here, a Slack bot token there, an API key for the CRM, and one more for the email provider. So before a single workflow ever fires, you’ve copied pieces of your working life onto a server that isn’t yours and trusted it to hold them.

The credential tax nobody films for the demo

The n8n demos are beautiful. You drag a Gmail node onto the canvas, connect it to a sheet, drop in a filter, and watch the whole thing run on its own. But what the clip leaves out is the twenty minutes before it, where you register an app in Google Cloud Console, configure a consent screen, generate a client secret, and paste it into a settings panel while praying you scoped the permissions correctly.

And that’s the friendly integration. The painful ones are the SaaS tools with no public API at all, or an API parked behind an enterprise tier that costs more than the automation will ever save you. Browser agents fill that gap for one stubborn reason: they never ask whether a service exposes an endpoint. They just read the page the way you do.

Your tab already did the hard part

You are already logged in. Right now, in the tab beside this one, you’ve got live authenticated sessions to Gmail, your CRM, your bank, your project tracker. And you proved who you were this morning, when you typed a password and tapped a code off your phone. But the integration model throws all of that away and asks you to prove it again, in a different format, to a different machine.

A browser agent does the obvious thing instead. So it works inside the tab you already opened, using the session you already established. No OAuth dance, no client secret, no third-party server quietly holding a token that can leak. Dassi lives in the Chrome side panel and acts where you act, so the list of services it can reach is just the list of sites you’re already signed into.

I wired up the same task twice

Last month I set up a small recurring job: pull new leads out of a web form, check each one against the CRM, and draft a follow-up email for anyone who wasn’t already in the system. The cloud-automation version ate most of an evening, and I want those hours back. I registered two OAuth apps, fought a redirect-URI mismatch for forty minutes, discovered the CRM’s free tier capped API calls at a number that made the whole thing pointless, and finally upgraded to a plan I didn’t want so the workflow would stop throwing 429 errors. So by the end it worked, and it was brittle, and every credential I’d minted was now living on infrastructure I’d never see. Then I did the same job with Dassi in the side panel. I described what I wanted in one sentence, and watched it open the form results, switch to the CRM tab, search each name, and write the drafts straight into the compose window. No app registration. No secret. No upgraded plan. Because it used the exact logins I was already staring at, and when it finished, nothing about my accounts had been copied anywhere. The damn thing just did the work where the work already lived.

Two bets on what automation actually is

SAP and n8n are betting that automation means a central hub wired to everything through formal integrations, and for the big back-office pipelines that shuttle data between systems of record, that bet is probably right. But most of what knocks a real hour out of my day isn’t a back-office pipeline. It’s the small, messy, login-gated stuff that lives in a browser and never had a clean API to begin with. And that’s the work the central hub can’t see, because it’s locked behind a session nobody ever handed it.

What $5.2 billion still can’t buy

A login you already have. SAP bought the plumbing for the back office. The tab in front of you was never part of the deal. So let them keep the hub. I’ll keep the tab.