Sanaf AI
Start free
Analytics

FullStory, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your FullStory account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Analytics
  • Connects with a key
  • 30 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What FullStory is

FullStory provides digital experience analytics APIs for managing users, events, sessions, exports, recording settings, privacy rules, and related organization data.

You paste in a key from your own FullStory account. It is kept encrypted, and you can withdraw it from inside FullStory whenever you like.

How a run works

One message in, the work done in FullStory.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in FullStory. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own FullStory account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

30 tools it already has

What it can do in FullStory

These are the ready-made tools your AI employee already has in FullStory. It is not limited to them, but it never has to be taught these.

  • Cancel OperationIrreversibly request cancellation of a cancelable in-progress FullStory operation, currently intended for segment exports. Confirm the operation before calling because a successful
  • Create AnnotationAdd a persistent annotation to the FullStory timeline for a point or time range. Warning: FullStory provides no matching delete endpoint, so a successful call cannot be cleaned up
  • Create Element BlockCreate a beta FullStory element recording or masking rule. Requires an Admin API key. Privacy-critical: an incorrect selector, UNMASK action, or live scope can expose sensitive dat
  • Create Extraction RuleCreate and immediately activate one FullStory beta extraction rule using the provider's nested rule, source, and mapping contract. Extraction can capture sensitive element, URL, he
  • Delete Element BlockPermanently delete a custom FullStory privacy element-block rule. This is irreversible: removing a block or mask can expose sensitive content in future recordings. Confirm the exac
  • Delete User DataPermanently delete a FullStory user and their associated data by FullStory-generated ID. This is an irreversible privacy mutation; confirm the target before calling.
  • Get Element BlockGet one FullStory privacy element-block rule by ID, including its exact selector source, recording or masking operation, platforms, and editability. Warning: this exposes privacy-s
  • Get Extraction RuleGet one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.
  • Get FullStory AccountValidate the connected API key and return its FullStory organization, identity, and API-key role. Do not use the role to infer paid product entitlements.
  • Get Import StatusGet status and success/error counts for an asynchronous FullStory event or user import job.
  • Get OperationGet detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.
  • Get Organization QuotasReturn current FullStory session and server-event quota usage, limits, and quota periods.
  • Get Recording SettingsGet one current FullStory recording-settings category. Privacy settings may contain sensitive configuration and large built-in rule sets; the complete provider response is preserve
  • Get SegmentGet metadata and the FullStory app URL for one segment.
  • Get UserRetrieve one user by FullStory-generated user ID, including profile fields and a FullStory app link.
  • Import EventsStart an asynchronous import of 1 to 50,000 server events. This permanently adds analytics data; use an idempotency key when retrying.
  • Import UsersStart an asynchronous upsert import of 1 to 50,000 users. This mutates personal profile data.
  • List DatasetsList beta datasets readable by the connected FullStory organization.
  • List Element BlocksReturn one page of custom and built-in FullStory privacy element-block rules. These rules determine what FullStory records or masks.
  • List Extraction RulesList all FullStory beta extraction rules matching one required scope and optional filters, together with current active-rule usage and limits.
  • List Import RecordsReturn one page of successful or failed records from a FullStory event or user import job, including failure details when requested.
  • List OperationsReturn one page of asynchronous FullStory operations, optionally filtered by state or type.
  • List Recording Settings HistoryReturn one page of historical FullStory recording settings for blocking, domain, geo, privacy, features, or targeting. Privacy history requires an Architect-level API key; the othe
  • List SegmentsReturn one page of FullStory segments, optionally filtered by creator.
  • List SessionsFind recent FullStory session replay links by application UID, email, or exact session UID. Provide at least one selector; sessionuid cannot be combined with uid or email. This is
  • Search UsersFind FullStory users by UID, email, display name, or identification state. Provide at least one of uid, email, displayname, or isidentified. A no-match 404 is returned as an empty
  • Set Extraction Rule ArchivedArchive a FullStory beta extraction rule to stop future capture, or unarchive it to resume capture. Warning: this changes collection behavior immediately. Archiving does not erase
  • Update Element BlockFully replace an editable beta FullStory element recording or masking rule. Requires an Admin API key. This is an irreversible privacy configuration update, not a patch: read the e
  • Update Extraction RulePartially update a FullStory beta extraction rule using last-write-wins semantics. Provide at least one of name, description, source, or mappings. Omitted fields remain unchanged;
  • Upsert UserCreate or update one FullStory user. Supplying fullstoryuserid updates that record; otherwise uid identifies an upsert. This mutates personal profile data.
Access, and who is in charge of it

You stay the boss of your FullStory account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own FullStory account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in FullStory is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in FullStory and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about FullStory

Can an AI employee really work inside FullStory?
Yes. It signs in to your own FullStory account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of FullStory?
No. Nothing moves and nothing is replaced. Your records stay in FullStory, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my FullStory account?
You paste in a key from your own FullStory account. It is kept encrypted, and you can withdraw it from inside FullStory whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in FullStory?
It has 30 ready-made tools in FullStory today, among them Cancel Operation, Create Annotation and Create Element Block. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use FullStory and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in FullStory and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in FullStory?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in FullStory is written down with what it did and when.