ActionBrowserbaseUpdated September 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.

Get Debug URL in Browserbase — start free All 6 Browserbase actions

Get Debug URL in Browserbase — start free

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
Session ID session_id	string	Required	Session 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.

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 run history shows the failed step with its input and the error message Browserbase returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Debug URL support batch operations?

Run Get Debug URL inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Browserbase's rate limits.

More actions