n8n 2.43: Browser Use Opens to Everyone, and the Supabase Line Matters More Than It Looks
No affiliate relationship: we hold no referral or affiliate link for n8n, so nothing on this page is monetised and no link below earns us anything. Every figure.
No affiliate relationship: we hold no referral or affiliate link for n8n, so nothing on this page is monetised and no link below earns us anything. Every figure was read off n8n’s own release notes and GitHub releases on 12 October 2026.
n8n released version 2.43 on 6 October 2026 under a headline that tells you what the release is for: “Browser Use now available to all users, plus 13 other features”. Browser Use had been gated. It is not any more.
That is the story, and the rest of the release is a list of sensible plumbing. But the plumbing contains one item that matters more than its changelog line suggests — OAuth2 on the Supabase node, which doubles as the path to Supabase’s MCP server — so it is worth reading past the headline.
A note on where to check this: n8n’s release-notes page at docs.n8n.io/release-notes returns a 404 shell to most automated fetchers. The machine-readable mirror at docs.n8n.io/release-notes.md serves the same content with the same release date, which is where our figures come from.
| What shipped | Where | Why it matters |
|---|---|---|
| Browser Use for all users | 2.43, 6 Oct | Agentic browsing is no longer restricted. It sits behind an admin setting, and the automatic credential-setup option is off by default. |
| Supabase OAuth2 | 2.43, 6 Oct | The Supabase node takes OAuth2, and the same credentials can enable the Supabase MCP server. |
| Databricks Job resource | 2.43, 6 Oct | Run, Get Job, Get Run and Get Run Output, so a workflow can trigger a Databricks job and collect its output. |
| Azure OpenAI deployment dropdown | 2.43, 6 Oct | Pick the deployment from a list rather than typing it. New nodes default to v1.1. |
| Nano Banana 2.1 and 2 Lite | 2.42.6, 9 Oct | Both added to the Google Gemini node’s image model list. |
| Deprecated nodes blocked | 2.42.6, 9 Oct | You can no longer create or update a workflow that uses a deprecated node. |
Browser Use, and the default that is off for a reason
Browser Use lets an n8n workflow drive a real browser rather than call an API — the escape hatch for every system that has no integration and never will. Opening it to all users is the single biggest capability change in this release.
Two caveats are in n8n’s own wording and both deserve attention. It sits behind an admin setting, so on a self-hosted or team instance it is not simply there for everyone the moment you upgrade; somebody has to turn it on. And the automatic credential-setup option is off by default.
That second default is the interesting one. An agent that can drive a browser and automatically pick up stored credentials is an agent that can log into things on your behalf without a human in the loop. n8n shipping that switch in the off position is the correct call, and it is worth leaving off unless you have a specific reason and a scoped set of credentials.
The Supabase line is doing more than it looks
“OAuth2 on the Supabase node” reads like admin housekeeping. What makes it notable is the second half of n8n’s sentence: the same credentials can enable the Supabase MCP server.
So one authorisation gets you both the node, for ordinary database steps inside a workflow, and an MCP endpoint your AI tooling can call directly. If you already run Supabase behind an n8n automation, this removes a credential-juggling step that previously made connecting an assistant to that data more trouble than it was worth.
The rest of the release
The remaining items are small and mostly quality-of-life:
- Crypto node: you can choose SHA-256 or SHA-1 for RSA-OAEP rather than taking whatever was hard-coded.
- Assistant panel: Cmd/Ctrl+J toggles it.
- Migration reports: impact categories replace severity labels, blocking issues are listed first, and there is a compatibility progress bar.
- NODES_EXCLUDE: now supports hiding generated AI tool variants, which is how you stop the node picker filling with auto-generated tool versions of everything.
- Gateway credits: promotions on eligible community nodes.
On the version numbers: 2.42.4 on 7 October and 2.42.5 on 8 October were bug fixes only, and 2.43.0 to 2.43.3 are the beta channel. 2.42.6 on 9 October is the most recent stable release, and nothing has been published since.
What we could not verify
Open questions, stated plainly
- Whether Browser Use costs anything to run. n8n says it is available to all users. It does not say whether executions consume Assistant credits, gateway credits or nothing at all.
- The Assistant credit allowances. n8n published a credits top-up scheme on 30 September, one day outside this window. A third-party pricing tracker records Starter Assistant credits dropping from 2,300 to 1,600 and Pro from 13,700 to 9,600 around 5 October, but cites no n8n source and we could not find an n8n-dated page confirming it. We are not asserting those figures. If you are budgeting on Assistant credits, check your own billing page.
- Which plans gate the admin setting. n8n names an admin setting but not which tiers or deployment types expose it.
- What breaks when deprecated nodes are blocked. 2.42.6 stops you creating or updating workflows that use them. n8n does not say whether existing workflows continue to run.
All figures above were read off n8n’s own release notes at docs.n8n.io/release-notes.md and its GitHub releases, on 12 October 2026. The HTML release-notes page returns a 404 to automated fetchers while the .md mirror serves correctly, so if you are checking our figures use the .md URL. If anything changes materially, this post gets a dated update box rather than a silent edit.
Frequently asked questions
What is in n8n 2.43?
Browser Use becoming available to all users, plus thirteen other features: OAuth2 on the Supabase node which can also enable the Supabase MCP server, a Databricks Job resource, an Azure OpenAI deployment dropdown, SHA-256 or SHA-1 selection for RSA-OAEP in the Crypto node, a Cmd/Ctrl+J shortcut for the Assistant panel, revised migration reports, NODES_EXCLUDE support for generated AI tool variants, and gateway credit promotions on eligible community nodes.
Is n8n Browser Use free to use now?
It is available to all users rather than a gated subset, but n8n does not state whether running it consumes credits of any kind. Availability and cost are two different claims, and only the first is published.
Why is Browser Use credential setup off by default?
n8n does not give a reason, but the risk is self-evident: an agent that drives a browser and automatically picks up stored credentials can sign into services without a human approving each step. Leaving it off is the safer default and we would leave it off unless you have a narrow, scoped reason to turn it on.
What changed in n8n 2.42.6?
Two things, on 9 October 2026: Nano Banana 2.1 and Nano Banana 2 Lite were added to the Google Gemini node’s image model list, and n8n now blocks creating or updating any workflow that uses a deprecated node.
Where are n8n release notes?
At docs.n8n.io/release-notes, though that page returns a 404 to many automated fetchers. The machine-readable mirror at docs.n8n.io/release-notes.md serves the same content reliably, and per-version detail is on the n8n GitHub releases page.