FullStory
for LuumenAI
Check FullStory privacy rules, quotas, and users, then make changes with approval.
Connect FullStory and your agent can read the account it is keyed to, session and server-event quotas, privacy element-block rules, extraction rules, segments, users, and the status of import and export operations. Changes — a new masking rule, a user import, an annotation on the timeline — are previewed and held for approval before they run.
The FullStory toolbox
30 tools: 18 read, 12 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet FullStory AccountValidate the connected API key and return its FullStory organization, identity, and API-key role.
- ReadGet Element BlockGet one FullStory privacy element-block rule by ID, including its exact selector source, recording or masking operation, platforms, and editability.
- ReadGet Extraction RuleGet one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.
- ReadGet Import StatusGet status and success/error counts for an asynchronous FullStory event or user import job.
- ReadGet OperationGet detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.
- ReadGet Organization QuotasReturn current FullStory session and server-event quota usage, limits, and quota periods.
- ReadGet Recording SettingsGet one current FullStory recording-settings category.
- ReadGet SegmentGet metadata and the FullStory app URL for one segment.
- ReadGet UserRetrieve one user by FullStory-generated user ID, including profile fields and a FullStory app link.
- ReadList DatasetsList beta datasets readable by the connected FullStory organization.
- ReadList Element BlocksReturn one page of custom and built-in FullStory privacy element-block rules.
- ReadList Extraction RulesList all FullStory beta extraction rules matching one required scope and optional filters, together with current active-rule usage and limits.
- ReadList Import RecordsReturn one page of successful or failed records from a FullStory event or user import job, including failure details when requested.
- ReadList OperationsReturn one page of asynchronous FullStory operations, optionally filtered by state or type.
- ReadList Recording Settings HistoryReturn one page of historical FullStory recording settings for blocking, domain, geo, privacy, features, or targeting.
- ReadList SegmentsReturn one page of FullStory segments, optionally filtered by creator.
- ReadList SessionsFind recent FullStory session replay links by application UID, email, or exact session UID.
- ReadSearch UsersFind FullStory users by UID, email, display name, or identification state.
- WriteCancel OperationIrreversibly request cancellation of a cancelable in-progress FullStory operation, currently intended for segment exports. Approval by default
- WriteCreate AnnotationAdd a persistent annotation to the FullStory timeline for a point or time range. Approval by default
- WriteCreate Element BlockCreate a beta FullStory element recording or masking rule. Approval by default
- WriteCreate Extraction RuleCreate and immediately activate one FullStory beta extraction rule using the provider's nested rule, source, and mapping contract. Approval by default
- WriteDelete Element BlockPermanently delete a custom FullStory privacy element-block rule. Approval by default
- WriteDelete User DataPermanently delete a FullStory user and their associated data by FullStory-generated ID. Approval by default
- WriteImport EventsStart an asynchronous import of 1 to 50,000 server events. Approval by default
- WriteImport UsersStart an asynchronous upsert import of 1 to 50,000 users. Approval by default
- WriteSet Extraction Rule ArchivedArchive a FullStory beta extraction rule to stop future capture, or unarchive it to resume capture. Approval by default
- WriteUpdate Element BlockFully replace an editable beta FullStory element recording or masking rule. Approval by default
- WriteUpdate Extraction RulePartially update a FullStory beta extraction rule using last-write-wins semantics. Approval by default
- WriteUpsert UserCreate or update one FullStory user. Approval by default
One prompt, start to finish
What a governed FullStory run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as cancel operation, create annotation, create element block, create extraction rule, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to FullStory — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put FullStory to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.