Resources · Zapier integration

Fullstory Zapier integrationAutomate Fullstory with Zapier.

The Fullstory Zapier integration gives you 4 triggers and 3 actions. All four triggers are instant, so a crash, a note or an alert reaches Zapier as it happens, even on the free plan. The actions summarize a session, update a user and send an event.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Fullstory Zapier integration is for

Fullstory records how people use your website or app and turns those sessions into replays and analytics. Plugging it into Zapier lets the moments Fullstory spots, a crash, a note, a custom event or an alert, start work in your other tools, and lets those tools feed user data and events back into Fullstory.

Three results justify the setup. A faster bug loop: Native Mobile Crash starts a Zap the moment a crash is detected in your mobile app, so the right people hear about it without watching a dashboard. Session context without the replay: Generate AI Session Summary turns a session into a written summary you can hand to someone who will never open Fullstory. Richer profiles: Set User Properties and Track Event push what your other tools know about a user into Fullstory, where it sits next to their sessions.

What Zapier cannot do here matters just as much. There is no search step, so a Zap cannot look up a user or a session before acting. There is no way to create a segment, edit an alert or delete anything. And the two user actions only work on people your site already identifies to Fullstory.

Weighing your options? There is our Make vs Zapier comparison, and our Zapier review is a good read before you commit. Operations below were read on the Zapier app page on 2026-10-01, version FullStoryCLIAPI@1.1.7.

Vocabulary

Zapier words in one minute

Seven terms come back throughout this page. Here they are in plain words.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event that starts the Zap, such as a crash Fullstory detects. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, like updating a user.
Task
The unit Zapier bills. One task equals one action your Zap completes successfully, and your plan counts those.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Fullstory account linked to Zapier once, then reused by every step of every Zap that touches Fullstory.
Cost

What a Fullstory Zap costs you

Fullstory is not a premium app, so it runs on the free plan. Zapier bills tasks, and only actions produce them.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps on the free planOne trigger and one action
  • Fullstory triggersInstant on every plan
  • Premium appNo

The trigger never costs a task, and neither does Zapier waiting for it. Every action that succeeds counts as one task, while a failed one is not counted at all. The free plan stops at two steps, one trigger and one action, so a filter turns the Zap into a multi-step Zap that needs a paid plan. On timing, the polling grid below does not slow you down here, because all four Fullstory triggers are instant.

Connect

Connect Fullstory to Zapier in three steps

  1. 01

    Open your Zapier apps

    In your Zapier account, open the Apps page and click + Add connection. You need a Fullstory account, plus access to any data you do not own yourself but want the Zap to touch.

  2. 02

    Pick Fullstory

    Search for Fullstory in the dialog, select it and click Add connection. A new tab opens on the Fullstory side so you can sign in with your usual Fullstory login.

  3. 03

    Sign in and allow access

    Log in with the Fullstory account your team uses and grant Zapier access. Every later Zap that uses Fullstory reuses this one connection, so the setup is done once.

First Zap

Your first Zap: a summary for crashes that matter

GoalWhen Fullstory detects a crash in your mobile app, the Zap asks for an AI summary of the session, but only for the crashes you decided to look at.

  1. 01

    Build: set the trigger

    Create a Zap, choose Fullstory as the app and Native Mobile Crash as the event, then pick the Fullstory connection you created above.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent crashes from your account, so you set up the next steps on a real one and can see which values it carries.

  3. 03

    Add the filter

    Click the plus icon and add Filter. Choose a field from the test result, a rule of the right type and a value. The filter makes this a multi-step Zap, which needs a paid plan.

  4. 04

    Add the summary action

    Add Fullstory again and choose Generate AI Session Summary. The action needs a Session ID: map it from the crash data if the test shows one.

  5. 05

    Test, then publish

    Test the action and read the summary that comes back. When it looks right, click Publish. Crashes from before that moment are not picked up.

Triggers

The 4 Fullstory triggers

4 events start a Zap when something happens in Fullstory, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Native Mobile Crash

Instant trigger

In Zapier“Triggers when a native mobile crash event is detected.”

Starts the Zap when Fullstory detects a crash in a native mobile app you track. It is the trigger for anyone who wants crashes to land with a person, not sit in a report.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a mobile product team that wants every crash to open a ticket in its bug tracker straight away.
Watch out
a bad release can crash many sessions at once, and each crash runs the Zap, so watch your task count.
2

Note Created

Instant trigger

In Zapier“Triggers when a user adds a note to a session.”

Fires when someone on your team adds a note to a Fullstory session. Notes are where people flag what they saw in a replay, so this trigger carries human judgment, not raw data.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a UX researcher who wants every note left on a replay to reach the design team's channel without copy-paste.
Watch out
the Zap only sees new notes; notes written before you publish never come through.
3

Custom Event

Instant trigger

In Zapier“Triggers when a custom event is detected in a FullStory session.”

Runs when a custom event shows up in a Fullstory session. You define those events yourself, so this trigger follows exactly the moments your product team decided were worth naming.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a SaaS team that wants each trial user who reaches a key step to show up in the CRM right then.
Watch out
if the Zap also runs Track Event, make sure the event it sends cannot set this trigger off again.
4

Segment Threshold Alert

Instant trigger

In Zapier“Triggers when a segment threshold alert in FullStory is fired.”

Fires when a segment threshold alert you set in Fullstory goes off. Instead of one session, it reports that a group of users crossed a line you care about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a growth lead who wants the on-call channel to hear when a segment suddenly spikes or drops.
Watch out
the alert itself is set up in Fullstory; Zapier only hears about it, it cannot create or change one.
Actions

The 3 Fullstory actions

Fullstory gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Generate AI Session Summary

Action

In Zapier“Generates a session summary using the Fullstory AI Session Summary API”

Asks Fullstory for a written AI summary of one session. You get what happened in prose, ready to drop into a ticket or a message.

When to use it
a support lead who wants a short account of the session behind each escalated complaint.
Watch out
the Session ID is required, so the step before must hand one over.
2

Set User Properties

Action

In Zapier“Updates user information in FullStory.”

Updates what Fullstory knows about a user, such as a plan or a role coming from another tool. The new properties then sit next to that person's sessions.

When to use it
a customer success team that wants the account tier from its billing tool visible on every replay.
Watch out
the Unique User Identifier must match the one your site set with FS.identify.
3

Track Event

Action

In Zapier“Sends an event to FullStory.”

Sends an event to Fullstory for a given user, so something that happened outside your product shows up on their timeline.

When to use it
a sales team that wants a signed contract, logged in another tool, recorded next to the buyer's sessions.
Watch out
both the Unique User Identifier and the Event Name are required; leave one empty and the action fails.
When it breaks

When a Fullstory Zap breaks

Zapier links no help article to Fullstory, so the known failure points are the ones every Zap shares, plus one that comes from Fullstory's own fields.

They rarely show on the day you publish. They show later, once real traffic arrives. Four to watch:

  • No backfill of past sessions

    A Zap only reacts to what happens after you switch it on. Crashes, notes and alerts from before that moment are never picked up.

  • An event Zap that feeds itself

    A Zap that writes into the place its own trigger watches sets itself off again and again. Check that Track Event cannot restart a Custom Event Zap.

  • A crash wave held back

    When a trigger suddenly returns a huge batch, Zapier's flood protection can hold the runs back. A broken release that crashes many sessions at once can produce such a batch.

  • A user Fullstory does not know

    Set User Properties and Track Event rely on the identifier set with FS.identify. Send another ID and the action has no one to attach to.
Need help

Need help automating Fullstory with Zapier?

A person reads every message.

FAQ

Fullstory Zapier integration: your questions

01Is the Fullstory Zapier integration free?
Yes, it runs on the free Zapier plan, since Fullstory is not a premium app. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. A Zap that summarizes each noted session fits. The moment you add a filter or a second action, the Zap becomes multi-step and you need a paid plan to keep it running.
02How many tasks does a Fullstory Zap use?
One per action that succeeds, and nothing for the trigger. A crash Zap with one summary action uses one task per crash. A Zap that summarizes a session, then updates the user, then sends an event, uses three tasks per run. Waiting for a crash or an alert costs nothing, and failed actions are not billed. With 100 tasks a month on the free plan, a noisy crash trigger can eat the budget fast.
03Do Fullstory triggers fire in real time?
Yes. All four Fullstory triggers are instant: Fullstory itself tells Zapier when a crash, a note, a custom event or an alert happens, and the Zap starts right away, without waiting for any check. The polling grid, which checks every 15 minutes on the free plan, does not apply to them. In the editor these triggers carry a lightning bolt. For crash alerts, that speed is the whole point: the person who has to fix the bug hears about it while the session is still fresh.
04What does it take to connect a Fullstory account?
A Fullstory account, plus access to anything you do not own but want the Zap to touch. Then three moves: open the Apps page in Zapier, click + Add connection and pick Fullstory, then sign in and grant access in the tab that opens. One connection serves every Zap afterwards. For the user actions, your site must also identify visitors with FS.identify, or there is no identifier to send, whatever the connection looks like.
05Why does Set User Properties not update the user?
Usually because the identifier does not match. Set User Properties and Track Event look for the Unique User Identifier that your site set with the FS.identify client API. If your Zap sends an email while your site identified people by an internal ID, Fullstory cannot tie the update to anyone. Check how your site calls FS.identify, then map that exact value into the action. A quick test with one known user tells you right away whether it matches.
06What if the Fullstory operation you need is not there?
Then a Zap cannot do it for Fullstory today. The app offers three actions and no search, so creating segments, editing alerts or looking up a session before acting is out of reach. The practical route is to keep that work inside Fullstory and use the four triggers to tell your other tools what happened. If a missing operation blocks a whole process, compare what other platforms offer for the same app.
07Zapier, Make or n8n for Fullstory?
Pick by criteria, not by a winner. First, check that the operation you need exists on each platform: on Zapier, Fullstory offers four instant triggers and three actions. Second, compare how each tool bills a run; on Zapier, only successful actions count. Third, think about who will maintain the automation and how comfortable they are with technical setups. Run your own process through those three points before deciding, and test the operation that matters most to you on each.
Same platform

Other docs you might need on this stack.

Browse all integrations