Integration

FullStory integration

Digital experience analytics platform providing session replay, heatmaps, and behavioral insights. Capture user interactions, track custom events, manage user data, export segment data, and integrate webhooks for real-time event notifications. Essential for understanding user behavior, identifying friction points, and optimizing digital experiences across web and mobile applications.

Connect FullStory How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in FullStory.Built from the 21 FullStory tools below, on the connection you add once.

Common FullStory use cases

Retrieve import and error counts for reporting
Monitor batch user import progress
Monitor batch event import progress
Build operations monitoring dashboard
Verify webhook endpoint configuration
Poll export job status until completion
Update user subscription plan information
Process GDPR right-to-be-forgotten requests
Decommission deprecated integration endpoints
Change webhook destination URL during migration

What you can do with FullStory

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

User, 7 operations

batch_create_usersBatch create usersPOSTCreates a batch user import job to upsert up to 50,000 users in a single asynchronous request. Users are created if they don't exist or updated if they do. Returns a job ID for tracking import progress.
create_userCreate userPOSTCreates or updates a user profile in FullStory with custom properties. Supports both identified users (with uid) and anonymous users. Properties are merged with existing data, with collision resolution favoring most recent values.
delete_userDelete userDELETEPermanently deletes all user data for the specified uid including sessions, events, custom properties, raw page files, and corresponding session data. Returns an operation ID for tracking deletion progress.
get_batch_user_import_jobGet batch user import jobGETRetrieves the current status of a batch user import job. Returns job ID, status (PROCESSING, COMPLETED, FAILED), import/error counts, and timestamps.
get_userGet userGETRetrieves detailed information about a specific user by their FullStory-assigned ID. Returns user profile data including uid, display name, email, deletion status, custom properties, optional schema, type conflicts, and direct application URL.
list_usersList usersGETRetrieves a paginated list of users matching the specified filter criteria. Supports filtering by uid, email, display name, and identification status. Returns user details including properties, schema, and FullStory application URLs.
update_userUpdate userPATCHUpdates an existing user's profile data by their FullStory-assigned ID. Allows modifying display name, email, and custom properties. Note: the uid value is immutable once set.

Webhook, 5 operations

create_webhook_endpointCreate webhook endpointPOSTCreates a new webhook endpoint that will receive event notifications at the specified URL. Configures which event types to subscribe to and provides a signing secret for payload verification.
delete_webhook_endpointDelete webhook endpointDELETEPermanently deletes a webhook endpoint, immediately stopping all event notifications to that destination. This action cannot be undone.
get_webhook_endpointGet webhook endpointGETRetrieves detailed configuration for a specific webhook endpoint including destination URL, subscribed event types, enabled status, and creation/modification timestamps.
list_webhook_endpointsList webhook endpointsGETRetrieves a paginated list of all webhook endpoints configured for the organization, including destination URLs, subscribed event types, and enabled status.
update_webhook_endpointUpdate webhook endpointPUTUpdates an existing webhook endpoint's configuration. Allows modifying the destination URL, subscribed event types, signing secret, and enabled/disabled status.

Event, 3 operations

batch_create_eventsBatch create eventsPOSTCreates multiple events in a single batch request for efficient high-volume event ingestion. Each event includes user association, name, optional timestamp, and custom properties.
create_eventCreate eventPOSTCreates a custom event with the specified name, timestamp, and properties. Events can be associated with a user (by uid) or a specific session (by session ID). Server time is used if timestamp is omitted.
get_batch_events_import_jobGet batch events import jobGETRetrieves the current status of a batch events import job. Returns job ID, status (PROCESSING, COMPLETED, FAILED), import/error counts, and timestamps.

Operation, 2 operations

get_operationGet operationGETRetrieves the current status of an asynchronous operation including type, state, progress percentage, timestamps, and results. Supports DELETE_USER, SEARCH_EXPORT, DELETE_SESSION, and other operation types.
list_operationsList operationsGETRetrieves a paginated list of all operation statuses including exports, deletions, and batch imports. Returns operation IDs, types, states, and timestamps for monitoring async workflows.

Segment, 2 operations

get_segmentGet segmentGETRetrieves detailed information about a specific segment by ID. Returns segment name, creator email, creation timestamp, and direct URL to the segment in the FullStory application.
list_segmentsList segmentsGETRetrieves a paginated list of saved segments in FullStory. Supports filtering by creator email and pagination for large result sets. Returns segment IDs, names, creators, creation dates, and application URLs.

Export, 1 operation

create_segment_exportCreate segment exportPOSTInitiates an asynchronous segment export job. Supports TYPE_EVENT (event data) or TYPE_INDIVIDUAL (user data) exports in FORMAT_JSON, FORMAT_CSV, or FORMAT_NDJSON. Returns an operation ID for tracking export progress.

Session, 1 operation

list_sessionsList sessionsGETRetrieves a list of session replay URLs for a user identified by email address or uid. Returns session IDs, creation times, and direct links to session replays in the FullStory application.

FullStory API rate limits

60 requests per minute

Rate limits vary by endpoint and key type. 429 responses include Retry-After header. Monthly server event quotas apply to batch operations.

These are the limits FullStory documents, not ones LiveContext measured. They can change and often depend on your plan, so check the FullStory documentation for current values.

Use FullStory from Claude Code, Cursor or Codex

Connect FullStory in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its FullStory operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect FullStory

Create your workspace
Sign up free. Nothing to install.
Connect FullStory once
Add your FullStory connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

FullStory integration FAQ

What can you do with the FullStory integration?

LiveContext exposes 21 operations on FullStory, covering user, webhook, event and operation. Common uses include Retrieve import and error counts for reporting, Monitor batch user import progress and Monitor batch event import progress.

What are the FullStory API rate limits?

FullStory documents 60 requests per minute. Rate limits vary by endpoint and key type. 429 responses include Retry-After header. Monthly server event quotas apply to batch operations. Limits are set by FullStory and can depend on your plan.