ActionFullStoryUpdated September 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.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
User UID uid | string | Required | – |
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.
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 run history shows the failed step with its input and the error message FullStory returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get FullStory User support batch operations?
Run Get FullStory User inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within FullStory's rate limits.
More actions