ActionFullStoryUpdated May 2026

How do I push an event to FullStory?

Short answer: Drop the "FullStory → Create FullStory Event" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 FullStory actions

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.

Google Sheets → FullStory

2 Google Sheets triggers

HubSpot → FullStory

18 HubSpot triggers

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 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 Create FullStory Event support batch operations?

Yes. Run Create FullStory Event inside a Loop node to process arrays. Tiny Command handles FullStory's rate limits automatically so you don't have to throttle manually.

More actions