--- title: "Switching from n8n: keep your flows, add real browsers | Scalebrowser" description: "Your n8n flows keep running in n8n. One HTTP call starts the browser part in Scalebrowser by webhook, in a profile with its own identity and logins, and Send Webhook hands the result back. There is no n8n node, and none is needed." canonical: "https://scalebrowser.net/switch/n8n" last_modified: "2026-11-15T13:22:44.000Z" --- > ## Documentation Index > Fetch the complete documentation index at: https://scalebrowser.net/llms.txt > Use this file to discover all available pages before exploring further. Switching from n8n # Keep n8n. Give its flows a real browser. Your n8n flow starts a Scalebrowser workflow by webhook. It works in a browser profile with its own identity and logins on your PC, and Send Webhook hands the result back. [Download free for Windows](https://scalebrowser.net/api/download/installer) [Read the webhook docs](https://scalebrowser.net/docs/events) Webhooks from Start at $19 · Every paid plan 7 days free · No credit card One email with the download link, nothing else. [Privacy](https://scalebrowser.net/privacy) [Read the webhook docs](https://scalebrowser.net/docs/events) Webhooks from Start at $19 · Every paid plan 7 days free · No credit card ## What stays, what starts fresh, what you gain. Your n8n flows keep running as they are. The browser part becomes a Scalebrowser workflow in four steps, with a browser of its own. ### Stays the same * Your n8n flows They keep running in n8n with their triggers and apps; one step sends the browser part over by webhook. * Data in as JSON Whatever JSON n8n posts arrives as the workflow's inputs, and its blocks read them by name. * Plain HTTPS A POST with JSON, an Idempotency-Key against double runs, and a signature check if you set a key. ### Starts fresh * The browser part It becomes a Scalebrowser workflow that starts with a Webhook trigger and runs in a profile on your PC. [1Start a workflow with a Webhook trigger](https://scalebrowser.net/switch/n8n#move-hook) * No n8n node There is no Scalebrowser node for n8n: a plain HTTP call to the workflow's address starts it. [2Call it from your n8n flow](https://scalebrowser.net/switch/n8n#move-call) * The result The address answers at once with 202, not with the result: Send Webhook or the run events bring it back. [3Send the result back](https://scalebrowser.net/switch/n8n#move-back) * Your logins on those sites The profile starts signed out: sign in once per site, or let your agent store the login in the vault without seeing it. [4Sign in once per site](https://scalebrowser.net/switch/n8n#move-logins) ### What you gain * A real browser per account Each profile has its own identity, proxy, cookies and logins; graphics card and screen come from your real PC. * Logins from the vault Log In from Vault types the password on its own site over https, and no AI block ever gets a value from the vault. * Captchas on the way Solve Captcha clears Cloudflare Turnstile, reCAPTCHA, hCaptcha, GeeTest and press-and-hold, so the run goes on. * A person approves first Ask for Approval waits for your OK by phone or email, and n8n hears of the wait as a run event. * Your agent calls it too Add an Agent Call trigger, and Claude Code or ChatGPT start the same workflow as a tool and get the result. ## The move, in four steps. Build the browser part once, then let n8n call it. 1. ### Step 1: Start a workflow with a Webhook trigger Build the browser part from blocks, then copy the trigger's secret address. Signed calls are one switch. 2. ### Step 2: Call it from your n8n flow Post the lead as JSON to that address. It answers at once with 202, while the workflow starts in its profile. 3. ### Step 3: Send the result back End with Send Webhook to an address of your n8n flow, or send the workflow's run events there, signed. 4. ### Step 4: Sign in once per site The profile starts signed out. Sign in once and it stays signed in, or let your agent store the login in the profile's vault without seeing the password. ## Before you wire it up, short answers. A line or two each. Every field and event is in the [webhook docs](https://scalebrowser.net/docs/events). ### No, a plain HTTP call does it. There is no n8n node and none is needed: your n8n flow posts JSON to the workflow's address, and takes the result back at an address of its own. ### ### ### ### ### ## Keep your n8n flows. Give them a real browser. Build the browser part as a workflow, call its address from n8n, and send the result back. [Download free for Windows](https://scalebrowser.net/api/download/installer) One email with the download link, nothing else. [Privacy](https://scalebrowser.net/privacy) Free plan to build and test · Webhooks from $19 · No credit card Free plan to build and test · Webhooks from $19 · No credit card