Switching from Zapier
Keep Zapier. Give its flows a real browser.
Your Zapier 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.
Webhooks from Start at $19 · Every paid plan 7 days free · No credit card
One email with the download link, nothing else. Privacy
Webhooks from Start at $19 · Every paid plan 7 days free · No credit card
What stays, what starts fresh, what you gain.
Your Zapier 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 Zapier flows
They keep running in Zapier with their triggers and apps; one step sends the browser part over by webhook.
Data in as JSON
Whatever JSON Zapier 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
- 1Start a workflow with a Webhook trigger
The browser part
It becomes a Scalebrowser workflow that starts with a Webhook trigger and runs in a profile on your PC.
- 2Call it from your Zapier flow
No Zapier app
There is no Scalebrowser app on Zapier: a plain HTTP call to the workflow's address starts it.
- 3Send the result back
The result
The address answers at once with 202, not with the result: Send Webhook or the run events bring it back.
- 4Sign in once per site
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.
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 Zapier 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 Zapier call it.
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.
Step 2: Call it from your Zapier flow
Post the lead as JSON to that address. It answers at once with 202, while the workflow starts in its profile.
Step 3: Send the result back
End with Send Webhook to an address of your Zapier flow, or send the workflow's run events there, signed.
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.
No, a plain HTTP call does it.
There is no Zapier app and none is needed: your Zapier flow posts JSON to the workflow's address, and takes the result back at an address of its own.
No, it comes back by webhook.
The address answers at once with 202 and a delivery id, before the browser starts. The result arrives when the run ends, through Send Webhook or the run events.
Start or higher.
Webhooks run through our server, so they come with every paid plan, from Start at $19 a month. Each is free for 7 days, without a card.
The relay holds the calls.
If your PC is off, the relay holds the calls by the rule you pick, all of them, only the latest or none, for 1 to 168 hours.
Only who knows its address.
The address ends in 24 random characters, and you can roll a new one anytime. With Require the key on, a call without your key's signature in X-Signature is turned away.
Yes, with For Each Profile.
The workflow runs the same steps over many profiles, each with its own identity and logins, as many at once as your plan runs.
Keep your Zapier flows. Give them a real browser.
Build the browser part as a workflow, call its address from Zapier, and send the result back.
One email with the download link, nothing else. 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