ActionBrowserbaseUpdated June 2026

How do I create a Browserbase session?

Short answer: You can create browser session in Browserbase by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Browserbase Create Browser Session action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this action All 6 Browserbase actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Viewport Width browser_settings_viewport_width	string	Optional	Viewport Width
Viewport Height browser_settings_viewport_height	string	Optional	Viewport Height
Keep Alive keep_alive	options	Optional	Keep Alive. Options: No, Yes
Proxies proxies	options	Optional	Proxies. Options: No, Yes

Sample request

{
  "browser_settings_viewport_width": "{{trigger.browser_settings_viewport_width}}",
  "browser_settings_viewport_height": "{{trigger.browser_settings_viewport_height}}",
  "keep_alive": "{{trigger.keep_alive}}",
  "proxies": "{{trigger.proxies}}"
}

Returns

{
  "id": "sess-abc",
  "status": "RUNNING",
  "connectUrl": "wss://...",
  "seleniumRemoteUrl": "https://..."
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Browser Session.

What does the Create Browser Session action do in Browserbase?

Starts a new headless Chromium session. Returns a session ID, connect URL (for Playwright), and debug URL (live VNC viewer). Optional context_id to reuse a saved auth profile, optional proxies for residential routing.

What inputs does Create Browser Session require?

Create Browser Session has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Browserbase returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Browser Session support batch operations?

Yes. Run Create Browser Session inside a Loop node to process arrays. TinyCommand handles Browserbase's rate limits automatically so you don't have to throttle manually.

More actions

Other Browserbase actions.

Action

Close Session

Stops a session early and releases the slot. Call this in a workflow's finally block to avoid orphaned sessions consuming slots. Sessions auto-close at the configured timeout (default 60min); explicit close saves cost on short jobs.

Action

Get Debug URL

Returns the short-lived live-viewer URL for an in-flight session. Open in a browser to watch the headless Chromium in real time — useful for debugging "why did the scrape break" or "what did the agent actually see" mysteries.

Action

Get Session Recording

Returns the rrweb-format recording of a completed session. Replay with the rrweb-player library to reconstruct the session's DOM mutations and user input. Useful for after-the-fact debugging of failed runs.

Action

Get Session

Returns metadata for a specific session — status, runtime, region, configured proxies. Useful for monitoring active sessions or auditing past runs.

Action

List Sessions

Paginated session history with status filters. Useful for "any orphaned sessions still consuming slots?" cleanup or for capacity planning around session quota usage.

How do I create a Browserbase session?

The fields this action accepts.

Apps that pair well as the trigger for Create Browser Session.

Questions about Create Browser Session.

Other Browserbase actions.