FullStory
FullStory product analytics and session capture
FullStory is the digital-experience-intelligence platform — session replay, heatmaps, funnels, frustration signals (rage clicks, error tracking) — used by product teams to understand actual user behaviour at scale. Tiny Command exposes two actions, no triggers (FullStory emits events for high-value moments via Lambda destinations; for "react to a specific event" workflows, configure the destination URL to a Tiny Command webhook trigger): Create Event (push a custom event into FullStory's event stream — extends what the JS SDK auto-captures with workflow-fired events), Get User (lookup a user by uid or email for context). The connection uses a FullStory API key from Settings → API. The Create Event pattern is useful for "log this server-side event into the user's FullStory session timeline" — e.g., a Stripe webhook fires "Payment Failed", the workflow Creates the event in FullStory so the support team replaying the session sees the payment failure on the timeline.
Do anything FullStory can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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 | 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. |
Pre-built FullStory workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect FullStory once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every FullStory field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the FullStory integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect FullStory to Tiny Command?
What FullStory triggers does Tiny Command support?
What FullStory actions can I run from a workflow?
Is the FullStory integration real-time?
Do I need to write code to use FullStory with Tiny Command?
How much does the FullStory integration cost?
More calendar & scheduling apps people connect.
Same category as FullStory, ordered by how often teams pair them. Hover the carousel to pause.
Do more with FullStory.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
