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.
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. |
{"project_slug": "{{trigger.project_slug}}","session_id": "{{trigger.session_id}}"}
{"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.
Any of these apps can fire this action as part of a workflow.