OtherReal-timeUpdated May 2026

LogRocket

LogRocket session replay and analytics

LogRocket is the session-replay-with-engineering-detail platform — captures user sessions with network requests, console logs, Redux state, and stack traces. Used by product and engineering teams to debug user-reported issues with the full context of what was happening in the app at that moment. Tiny Command exposes two actions, no triggers: List Sessions (paginated browse with filters), Get Session (one session's metadata plus a replay URL). The connection uses a LogRocket API key from organisation settings. The Get Session action returns the replay URL — embed in support tickets or Slack notifications so engineers can immediately watch what the user did.

Connect LogRocket

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything LogRocket can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get LogRocket Session	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.	2 fields	View →
List LogRocket Sessions	Paginated sessions with filters by user, custom-property values, error counts, time range. For "find sessions for this customer with errors" diagnostic workflows.	2 fields	View →

Recipes

Pre-built LogRocket workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

LogRocket → Slack alerts

AI-triage every LogRocket event, ping the right channel only when it matters.

LogRocket → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

LogRocket → Notion database

Turn LogRocket into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect LogRocket once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every LogRocket field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the LogRocket integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect LogRocket to Tiny Command?

Open the Tiny Command workflow builder, drop in a LogRocket node, and click Connect. Authorize LogRocket once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What LogRocket triggers does Tiny Command support?

Tiny Command focuses on outbound actions for LogRocket today. Use Tiny Command's universal Webhook or Schedule trigger to start LogRocket workflows, then run any LogRocket action you need.

What LogRocket actions can I run from a workflow?

2 LogRocket actions are available out of the box, covering other operations like "Get LogRocket Session". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the LogRocket integration real-time?

LogRocket actions execute synchronously inside your workflow. Tiny Command waits for LogRocket's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use LogRocket with Tiny Command?

No. Every LogRocket trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any LogRocket API endpoint directly.

How much does the LogRocket integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The LogRocket integration itself has no per-app surcharge.