LogRocket
List user sessions recorded by LogRocket.
Connect
Auth type: API key (secret_text). Paste the API key (or token) from the provider's settings into the connect dialog. It is encrypted at rest and only decrypted on the server when an action runs.
- In the editor: Backend panel, Integrations tab, then Connect. This connects it for the project.
- For every project in a workspace: Workspace settings, Integrations.
- Owners and admins choose which integrations members may connect in the admin panel (Integrations tab), and can attach their own OAuth app there.
Call it from a workflow
Pass the action name and its input. The call resolves with { success, output, error? }; a missing connection resolves with success false and the reason. See ctx.integrations.invoke and ctx.integrations.call.
// .workflow.js (native ctx)
export async function run(ctx) {
const res = await ctx.integrations.invoke("logrocket", "identifyUser", {
"orgId": "<organization id>",
"appId": "<app id>",
"userId": "<user id>"
});
if (!res.success) throw new Error(res.error);
ctx.log.info("LogRocket answered", { output: res.output });
}// defineWorkflow module (@app/sdk ctx)
import { defineWorkflow } from "@app/sdk";
export default defineWorkflow({
id: "logrocket-identifyuser",
name: "LogRocket: Identify User",
description: "Calls LogRocket when a row is created.",
trigger: { type: "entity_event", entity: "tickets", event: "created" },
async run(ctx, event) {
const res = await ctx.integrations.call("logrocket", {
"action": "identifyUser",
"orgId": "<organization id>",
"appId": "<app id>",
"userId": "<user id>"
}) as { success: boolean; error?: string };
if (!res.success) throw new Error(res.error);
},
});curl -X POST "$APP_ORIGIN/__appbricx/connector-proxy/logrocket/identifyUser" \
-H "Authorization: Bearer $APP_KEY" \
-H "content-type: application/json" \
-d '{"props":{"orgId":"<organization id>","appId":"<app id>","userId":"<user id>"}}'Actions
identifyUserin catalog
Identify User. Create or update user information and traits in LogRocket to contextualize user behavior.
| Input | Type | Description |
|---|---|---|
orgIdrequired | text | Your LogRocket organization ID (found in Settings > General Settings, or in your App ID before the slash) |
appIdrequired | text | Your LogRocket app/project ID (found in Settings > General Settings, or in your App ID after the slash) |
userIdrequired | text | The unique identifier for the user |
nameoptional | text | The user's name (max 1024 characters) |
emailoptional | text | The user's email address (max 1024 characters) |
timestampoptional | date-time (ISO) | Unix timestamp in milliseconds indicating when this data was collected (optional) |
traitsoptional | object | User traits as key-value pairs (e.g., {"plan": "free", "age": 43}). Values will be converted to strings. |
requestHighlightsin catalog
Request Highlights. Request session highlights for a user. Results will be sent to the webhook URL when ready.
| Input | Type | Description |
|---|---|---|
orgIdrequired | text | Your LogRocket organization ID (found in Settings > General Settings, or in your App ID before the slash) |
projectIdrequired | text | Your LogRocket project ID (found in Settings > General Settings, or in your App ID after the slash) |
userEmailoptional | text | The email of the user to get highlights for |
userIdoptional | text | The ID of the user from LogRocket.identify() calls |
timeRangeStartoptional | date-time (ISO) | Start of the time range for sessions (optional) |
timeRangeEndoptional | date-time (ISO) | End of the time range for sessions (optional) |
webhookUrlrequired | text | URL where highlights results will be posted when ready. You can get this from the "Highlights Ready" trigger. |
Details
- Id
logrocket- Category
- Analytics
- Tags
- session-replay, debugging, frontend, ux
- Package
@activepieces/piece-logrocket@0.1.4- Tier
- Community