ActionBrowserbaseUpdated September 2026

How do I list Browserbase sessions?

Short answer: You can list sessions in Browserbase by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Browserbase List Sessions 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.

List Sessions in Browserbase — start free All 6 Browserbase actions

List Sessions 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
Status status	options	Optional	Status. Options: All, Running, Completed

Sample request

{
  "status": "{{trigger.status}}"
}

Returns

[
  {
    "id": "sess_abc",
    "status": "RUNNING",
    "createdAt": "2026-05-10T10:00:00Z"
  }
]

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

Triggered by

Apps that pair well as the trigger for List Sessions.

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 List Sessions.

What does the List Sessions action do in Browserbase?

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

What inputs does List Sessions require?

List Sessions 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 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 List Sessions support batch operations?

Run List Sessions 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