Connect FullStory to your AI agent
FullStory provides digital experience analytics APIs for managing users, events, sessions, exports, recording settings, privacy rules, and related organization data.
We set up the connection using your own FullStory account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.
Actions
What your agent can do in FullStory
Each one is a real action the agent can take on its own, the same things a person clicking around FullStory could do. Read-only by default; write actions are confirmed against your policy.
- Cancel Operation Irreversibly request cancellation of a cancelable in-progress FullStory operation, currently intended for segment exports. Confirm the operation before calling because a successful cancellation request cannot be undone.
- Create Annotation Add 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 through this API.
- Create Element Block Create 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 data, while EXCLUDE or MASK can suppress u…
- Create Extraction Rule Create and immediately activate one FullStory beta extraction rule using the provider's nested rule, source, and mapping contract. Extraction can capture sensitive element, URL, header, or body values and can materially…
- Delete Element Block Permanently 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 exact custom rule first; built-in rules can…
- Delete User Data Permanently delete a FullStory user and their associated data by FullStory-generated ID. This is an irreversible privacy mutation; confirm the target before calling.
- Get FullStory Account Validate 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 Element Block Get one FullStory privacy element-block rule by ID, including its exact selector source, recording or masking operation, platforms, and editability. Warning: this exposes privacy-sensitive recording configuration. This…
- Get Extraction Rule Get one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.
- Get Import Status Get status and success/error counts for an asynchronous FullStory event or user import job.
- Get Operation Get detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.
- Get Organization Quotas Return current FullStory session and server-event quota usage, limits, and quota periods.
- Get Recording Settings Get one current FullStory recording-settings category. Privacy settings may contain sensitive configuration and large built-in rule sets; the complete provider response is preserved.
- Get Segment Get metadata and the FullStory app URL for one segment.
- Get User Retrieve one user by FullStory-generated user ID, including profile fields and a FullStory app link.
- Import Events Start an asynchronous import of 1 to 50,000 server events. This permanently adds analytics data; use an idempotency key when retrying.
- Import Users Start an asynchronous upsert import of 1 to 50,000 users. This mutates personal profile data.
- List Datasets List beta datasets readable by the connected FullStory organization.
- List Element Blocks Return one page of custom and built-in FullStory privacy element-block rules. These rules determine what FullStory records or masks.
- List Extraction Rules List all FullStory beta extraction rules matching one required scope and optional filters, together with current active-rule usage and limits.
- List Import Records Return one page of successful or failed records from a FullStory event or user import job, including failure details when requested.
- List Operations Return one page of asynchronous FullStory operations, optionally filtered by state or type.
- List Recording Settings History Return one page of historical FullStory recording settings for blocking, domain, geo, privacy, features, or targeting. Privacy history requires an Architect-level API key; the other categories require Standard or higher.
- List Segments Return one page of FullStory segments, optionally filtered by creator.
- List Sessions Find recent FullStory session replay links by application UID, email, or exact session UID. Provide at least one selector; session_uid cannot be combined with uid or email. This is a filtered single-page lookup, not an…
- Search Users Find FullStory users by UID, email, display name, or identification state. Provide at least one of uid, email, display_name, or is_identified. A no-match 404 is returned as an empty result page.
- Set Extraction Rule Archived Archive 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 data already collected, and data not ca…
- Update Element Block Fully 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 existing rule first and provide every re…
- Update Extraction Rule Partially 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; read the current rule first. Warning: c…
- Upsert User Create or update one FullStory user. Supplying fullstory_user_id updates that record; otherwise uid identifies an upsert. This mutates personal profile data.
Setup
How we connect it
- 1
Connect your account
You create a key in FullStory, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.
- 2
Set the guardrails
Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.
- 3
We keep it running
Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.
FAQ
FullStory questions, answered.
With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions FullStory's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.
Ready to put FullStory to work?
Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.
All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by FullStory.