ActionLogRocketUpdated September 2026
How do I fetch a LogRocket session?
Short answer: You can get logrocket session in LogRocket by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the LogRocket Get LogRocket Session action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | – |
Session ID session_id | string | Required | The Session ID assigned by Logrocket. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Sample request
{"project_slug": "{{trigger.project_slug}}","session_id": "{{trigger.session_id}}"}
Returns
{"id": "sess_abc","url": "https://app.logrocket.com/...","user": {"id": "u_1","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 Get LogRocket Session.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get LogRocket Session.
What does the Get LogRocket Session action do in LogRocket?
Returns session metadata plus a replay URL. Embed the replay URL in support tickets, Slack notifications, Linear issues — gives engineers immediate context for user-reported issues.
What inputs does Get LogRocket Session require?
Required: Project Slug, 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 LogRocket returns an error?
The run history shows the failed step with its input and the error message LogRocket 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 Get LogRocket Session support batch operations?
Run Get LogRocket Session 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 LogRocket's rate limits.
More actions