---
title: "FullStory integration for LuumenAI"
url: "https://www.luumen.ai/integrations/fullstory/"
entity: SoftwareIntegration
category: "Databases & data platforms"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# FullStory integration for LuumenAI

Check FullStory privacy rules, quotas, and users, then make changes with approval.

## What LuumenAI can do with FullStory

LuumenAI connects to FullStory with an API token and exposes 30 tools (18 read-only · 6 write · 6 destructive). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: API token
- Tools available: 30 tools (18 read-only · 6 write · 6 destructive)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: Databases & data platforms

## About FullStory with LuumenAI

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.

## Example tools

Read-only (18 in total):

- `FULLSTORY_GET_ACCOUNT` — Validate the connected API key and return its FullStory organization, identity, and API-key role.
- `FULLSTORY_GET_ELEMENT_BLOCK` — Get one FullStory privacy element-block rule by ID, including its exact selector source, recording or masking operation, platforms, and editability.
- `FULLSTORY_GET_EXTRACTION_RULE` — Get one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.
- `FULLSTORY_GET_IMPORT_STATUS` — Get status and success/error counts for an asynchronous FullStory event or user import job.
- `FULLSTORY_GET_OPERATION` — Get detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.
- `FULLSTORY_GET_ORGANIZATION_QUOTAS` — Return current FullStory session and server-event quota usage, limits, and quota periods.
- `FULLSTORY_GET_RECORDING_SETTINGS` — Get one current FullStory recording-settings category.
- `FULLSTORY_GET_SEGMENT` — Get metadata and the FullStory app URL for one segment.

Write and destructive (12 in total, subject to configured approval policy):

- `FULLSTORY_CANCEL_OPERATION` — Irreversibly request cancellation of a cancelable in-progress FullStory operation, currently intended for segment exports.
- `FULLSTORY_CREATE_ANNOTATION` — Add a persistent annotation to the FullStory timeline for a point or time range.
- `FULLSTORY_CREATE_ELEMENT_BLOCK` — Create a beta FullStory element recording or masking rule.
- `FULLSTORY_CREATE_EXTRACTION_RULE` — Create and immediately activate one FullStory beta extraction rule using the provider's nested rule, source, and mapping contract.
- `FULLSTORY_DELETE_ELEMENT_BLOCK` — Permanently delete a custom FullStory privacy element-block rule.
- `FULLSTORY_DELETE_USER_DATA` — Permanently delete a FullStory user and their associated data by FullStory-generated ID.
- `FULLSTORY_IMPORT_EVENTS` — Start an asynchronous import of 1 to 50,000 server events.
- `FULLSTORY_IMPORT_USERS` — Start an asynchronous upsert import of 1 to 50,000 users.

## Frequently asked questions

### How does LuumenAI connect to FullStory?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in FullStory on its own?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### Is there an audit trail?

Every call to FullStory — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/fullstory/