Short answer: Drop the "LogRocket → Get LogRocket Session" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
Triggered by anything in the catalog. Free tier available. No credit card.