Skip to content
ActionBrowserbaseUpdated May 2026

How do I list Browserbase sessions?

Short answer: Drop the "BrowserbaseList Sessions" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Status
status
optionsOptionalStatus. 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.

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

Other Browserbase actions.

Send list sessions from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.