ActionLogRocketUpdated May 2026

How do I list LogRocket sessions?

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

Use this action All 2 LogRocket 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
Project Slug project_slug	string	Required	—
Limit limit	string	Optional	—

Sample request

{
  "project_slug": "{{trigger.project_slug}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "items": [
    {
      "id": "sess_abc",
      "url": "https://app.logrocket.com/...",
      "user": {
        "name": "Jane"
      },
      "duration": 12000
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List LogRocket Sessions.

Any of these apps can fire this action as part of a workflow.

Google Sheets → LogRocket

2 Google Sheets triggers

HubSpot → LogRocket

18 HubSpot triggers

FAQ

Questions about List LogRocket Sessions.

What does the List LogRocket Sessions action do in LogRocket?

Paginated sessions with filters by user, custom-property values, error counts, time range. For "find sessions for this customer with errors" diagnostic workflows.

What inputs does List LogRocket Sessions require?

Required: Project Slug. 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 LogRocket 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 LogRocket Sessions support batch operations?

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

More actions