ActionFullStoryUpdated September 2026
How do I push an event to FullStory?
Short answer: You can create fullstory event in FullStory by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the FullStory Create FullStory Event action to a workflow, map its 3 inputs 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 user_uid | string | Required | – |
Event Name name | string | Required | – |
Properties (JSON) properties_json | string | Optional | – |
Sample request
{"user_uid": "{{trigger.user_uid}}","name": "{{trigger.name}}","properties_json": "{{trigger.properties_json}}"}
Returns
{"id": "event_abc"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Create FullStory Event.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create FullStory Event.
What does the Create FullStory Event action do in FullStory?
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.
What inputs does Create FullStory Event require?
Required: User UID, Event Name. 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 Create FullStory Event support batch operations?
Run Create FullStory Event 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