Get Session Recording: Browserbase action

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

[
  {
    "data": {},
    "type": 1,
    "timestamp": 1700000000000
  }
]

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

FAQ

Questions about Get Session Recording.

What does the Get Session Recording action do in Browserbase?

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.

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

Yes. Run Get Session Recording 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