Start free
ActionFullStoryUpdated June 2026

How do I fetch a FullStory user?

Short answer: You can get fullstory user in FullStory by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the FullStory Get FullStory User action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get FullStory User in FullStory — start free All 2 FullStory actions
Get FullStory User in FullStory — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
User UID
uid
stringRequired–
Sample request
{
  "uid": "{{trigger.uid}}"
}
Returns
{
  "users": [
    {
      "id": "u_abc",
      "uid": "user_1",
      "email": "jane@x.com",
      "display_name": "Jane"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get FullStory User.

Any of these apps can fire this action as part of a workflow.

Gmail → FullStory
1 Gmail triggers
Slack → FullStory
13 Slack triggers
Google Sheets → FullStory
2 Google Sheets triggers
HubSpot → FullStory
18 HubSpot triggers
FAQ

Questions about Get FullStory User.

What does the Get FullStory User action do in FullStory?
Returns a user by uid or email with associated session count and last-seen timestamp. The lookup for resolving FullStory user IDs when cross-referencing with CRM records.
What inputs does Get FullStory User require?
Required: User UID. 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 FullStory returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Get FullStory User support batch operations?
Yes. Run Get FullStory User inside a Loop node to process arrays. TinyCommand handles FullStory's rate limits automatically so you don't have to throttle manually.
More actions

Other FullStory actions.

Action
Create FullStory Event
Pushes a custom server-side event into FullStory's event stream — extends the JS SDK's browser-side capture. For "log server-side payment failure into the user's FullStory session timeline" patterns that give support staff full context on replay.
Get FullStory User in FullStory — start free