Start free
ActionBrowserbaseUpdated June 2026

How do I view a Browserbase session live?

Short answer: You can get debug url in Browserbase by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Browserbase Get Debug URL action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 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.

FieldTypeRequiredDescription
Session ID
session_id
stringRequiredSession ID (required)
Sample request
{
  "session_id": "{{trigger.session_id}}"
}
Returns
{
  "wsUrl": "wss://x.com",
  "debuggerUrl": "https://x.com/d",
  "debuggerFullscreenUrl": "https://x.com"
}

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

Triggered by

Apps that pair well as the trigger for Get Debug URL.

Any of these apps can fire this action as part of a workflow.

Gmail → Browserbase
1 Gmail triggers
Slack → Browserbase
13 Slack triggers
Google Sheets → Browserbase
2 Google Sheets triggers
HubSpot → Browserbase
18 HubSpot triggers
FAQ

Questions about Get Debug URL.

What does the Get Debug URL action do in Browserbase?
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.
What inputs does Get Debug URL require?
Required: Session ID. Every input accepts a static value or a variable from any upstream node in your workflow.
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 Get Debug URL support batch operations?
Yes. Run Get Debug URL 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
Create Browser Session
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.
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.