ActionBrowserbaseUpdated May 2026

How do I fetch Browserbase session details?

Short answer: Drop the "Browserbase → Get Session" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

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
Session ID session_id	string	Required	Session ID (required)

Sample request

{
  "session_id": "{{trigger.session_id}}"
}

Returns

{
  "id": "sess-abc",
  "status": "COMPLETED",
  "duration": 12000
}

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

Triggered by

Apps that pair well as the trigger for Get Session.

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 Session.

What does the Get Session action do in Browserbase?

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

What inputs does Get Session 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 Session support batch operations?

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

More actions