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.
ActionTry it
Integrate FullStory
with your AI CRM
FullStory provides digital experience analytics APIs for managing users, events, sessions, exports, recording settings, privacy rules, and related organization data.
Explore Triggers and Actions
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.
ActionTry it
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 useful recording. Review every field and prefer preview scope before calling.
ActionTry it
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 increase collected data volume. Archiving later only stops future capture; it does not erase data already collected. Review selectors, network filters, mapping targets, property scope, and privacy policy before calling. The beta contract may change without notice. Requires an Architect or Admin API key.
ActionTry it
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 cannot be deleted. This API is in beta and may change without notice.
ActionTry it
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.
ActionTry it
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 API is in beta; functionality and documentation are subject to breaking change without notification.
ActionTry it
Get Extraction Rule
Get one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.
ActionTry it
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.
ActionTry it
Get Import Status
Get status and success/error counts for an asynchronous FullStory event or user import job.
ActionTry it
Get Operation
Get detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.
ActionTry it
Get Organization Quotas
Return current FullStory session and server-event quota usage, limits, and quota periods.
ActionTry it
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.
ActionTry it
Get Segment
Get metadata and the FullStory app URL for one segment.
ActionTry it
Get User
Retrieve one user by FullStory-generated user ID, including profile fields and a FullStory app link.
ActionTry it
Import Events
Start an asynchronous import of 1 to 50,000 server events. This permanently adds analytics data; use an idempotency key when retrying.
ActionTry it
Import Users
Start an asynchronous upsert import of 1 to 50,000 users. This mutates personal profile data.
ActionTry it
List Datasets
List beta datasets readable by the connected FullStory organization.
ActionTry it
List Element Blocks
Return one page of custom and built-in FullStory privacy element-block rules. These rules determine what FullStory records or masks.
ActionTry it
List Extraction Rules
List all FullStory beta extraction rules matching one required scope and optional filters, together with current active-rule usage and limits.
ActionTry it
List Import Records
Return one page of successful or failed records from a FullStory event or user import job, including failure details when requested.
ActionTry it
List Operations
Return one page of asynchronous FullStory operations, optionally filtered by state or type.
ActionTry it
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.
ActionTry it
List Segments
Return one page of FullStory segments, optionally filtered by creator.
ActionTry it
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 unfiltered or paginated list; a no-match 404 returns an empty sessions list.
ActionTry it
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.
ActionTry it
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 captured while the rule is archived cannot be recovered by unarchiving. Confirm the rule ID and intended state before calling. Requires an Architect or Admin API key.
ActionTry it
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 required replacement field. An incorrect selector, UNMASK action, or live scope can expose sensitive data, while EXCLUDE or MASK can suppress desired recording.
ActionTry it
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: changing a rule's source or mappings changes what FullStory captures and may affect privacy, downstream analytics, and data volume.
ActionTry it
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.
ActionTry it
How the FullStory integration works
The FullStory integration connects your Dench AI CRM directly to FullStory, so agents can read and act on your FullStory data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
30 actions are available for agents to invoke on your behalf. Every call runs through FullStory's own authorization, scoped to the account you connect.
Set up FullStory in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find FullStory and click Connect — you'll authorize access through FullStory's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use FullStory in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the FullStory integration work with Dench?
The Dench FullStory integration connects your AI CRM to FullStory, so AI agents can work with your FullStory data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with FullStory via Dench?
The FullStory integration currently exposes 30 actions, including Cancel Operation, Create Annotation, Create Element Block, Create Extraction Rule, Delete Element Block, and Delete User Data. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect FullStory to Dench?
No. You connect FullStory from your Dench workspace using FullStory's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the FullStory integration secure?
Connections are authorized through FullStory's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the FullStory connection from your workspace settings at any time.