> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Fullstory

The Fullstory connector lets your AI agent act in each user's Fullstory account. Each user connects their own Fullstory API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 30 tools.

**Authentication:** API Key
**Categories:** Analytics
**Tools:** 30: 19 read, 9 write, 2 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=FULLSTORY)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Fullstory connection

   In **AgentKit > Connections**, create a Fullstory connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'fullstory'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Fullstory:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'fullstory_me_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "fullstory"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Fullstory:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="fullstory_me_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Fullstory credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'fullstory_events_batch_import_errors_list',
  toolInput: {
    job_id: '<job_id>',
  },
  connector: 'fullstory',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="fullstory_events_batch_import_errors_list",
    tool_input={
        "job_id": "<job_id>",
    },
    connection_name="fullstory",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `fullstory_events_batch_import_errors_list`

List Event Batch Import Errors · Read-only

List the events that failed in a batch event import job, one page at a time.
Returns each failed event with an error code and message, plus next_page_token.
Use this after fullstory_events_batch_import_get reports failures.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): The batch event import job ID returned by fullstory_events_batch_import_create. Example: MTI4NjYxNjM0MjM1NzQ0MzQ5OA.
- `page_token` (`string`, optional): Token for the next page, from the next_page_token of the previous fullstory_events_batch_import_errors_list response. Leave empty for the first page.

Example input: `{"job_id":"<job_id>"}`

### `fullstory_events_batch_import_get`

Get Event Batch Import Status · Read-only

Get the status of a batch event import job.
Returns the job (id, status, created and finished times) and the counts of imported events and errors.
Use this to poll a job from fullstory_events_batch_import_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): The batch event import job ID returned by fullstory_events_batch_import_create. Example: MTI4NjYxNjM0MjM1NzQ0MzQ5OA.

Example input: `{"job_id":"<job_id>"}`

### `fullstory_events_batch_imports_list`

List Event Batch Import Results · Read-only

List the events imported successfully by a batch event import job, one page at a time.
Returns each imported event's details, plus next_page_token.
Use this to confirm which events landed after a batch import.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): The batch event import job ID returned by fullstory_events_batch_import_create. Example: MTI4NjYxNjM0MjM1NzQ0MzQ5OA.
- `include_schema` (`boolean`, optional): Set to true to include the property type schema in the response. Defaults to false.
- `page_token` (`string`, optional): Token for the next page, from the next_page_token of the previous fullstory_events_batch_imports_list response. Leave empty for the first page.

Example input: `{"job_id":"<job_id>"}`

### `fullstory_me_get`

Get API Key Info · Read-only

Check the connected Fullstory API key.
Returns the key's orgId, the email of the user it belongs to, its role (USER for Standard, ARCHITECT or ADMIN) and scopes.
Use this to test the connection or to see whether the key can call Architect-level tools.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `fullstory_operation_get`

Get Operation · Read-only

Get the status of one Fullstory background operation, such as a segment export or user deletion.
Returns the operation's type, state (PENDING, COMPLETED or FAILED), estimated percent complete, errorDetails and results; a completed export's results hold its searchExportId and expiry.
Use this to poll an operation. Use fullstory_search_export_results_get to download a completed export.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The operation ID, for example the operationId returned by fullstory_segment_export_create. Example: 4b1c8f2e-0f3d-4c8b-9a7e-2d5f6c1b3a90.

Example input: `{"id":"<id>"}`

### `fullstory_operations_list`

List Operations · Read-only

List Fullstory's background operations (exports and deletions), ongoing and completed, optionally by state or type.
Returns each operation's id, type, state, estimated percent complete, results and timestamps, plus nextPaginationToken.
Use this to find recent exports or deletions. Use fullstory_operation_get for one operation.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `limit` (`integer`, optional): Maximum number of operations to return, up to 100 (the default).
- `paginationToken` (`string`, optional): Token for the next page, from the previous fullstory_operations_list response. Keep the other filters the same between pages.
- `state` (`string`, optional): Only return operations in this state. One of: `PENDING`, `COMPLETED`, `FAILED`.
- `type` (`string`, optional): Only return operations of this type. One of: `DELETE_USER`, `SEARCH_EXPORT`, `DELETE_SESSION`, `DELETE_SEGMENT_SESSIONS`, `DELETE_SEGMENT_USERS`.

Example input: `{}`

### `fullstory_quotas_get`

Get Quotas · Read-only

Get the Fullstory organization's quota usage, including session and server event quotas.
Returns each quota with its limit, usage and period.
Use this before large imports to check remaining capacity.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `fullstory_search_export_results_get`

Get Export Download Link · Read-only

Get a temporary download URL for a completed, unexpired segment export. Needs an Architect or Admin API key.
Returns location, a temporary URL to download the exported file, and when it expires.
Use this after fullstory_operation_get shows the export COMPLETED; pass the searchExportId from its results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The searchExportId from the results of a completed SEARCH_EXPORT operation. Example: 4f2c6d9a-1b3e-4c5d-8e7f-0a1b2c3d4e5f.

Example input: `{"id":"<id>"}`

### `fullstory_segment_get`

Get Segment · Read-only

Get one saved Fullstory segment by ID.
Returns the segment's id, name, creator, creation time and URL.
Use this when you have a segment ID, for example from a Fullstory segment URL. Use fullstory_segments_list to find one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The segment ID from fullstory_segments_list or from a Fullstory segment URL. Example: everyone.

Example input: `{"id":"<id>"}`

### `fullstory_segments_list`

List Segments · Read-only

List the saved segments in Fullstory, one page at a time, optionally only those created by one user.
Returns each segment's id, name, creator, creation time and URL, plus nextPaginationToken.
Use this to find a segment ID for fullstory_segment_export_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `creator` (`string`, optional): Only return segments created by the Fullstory user with this email. Example: daniel.falko@example.com.
- `limit` (`integer`, optional): Maximum number of results to return, up to 100. Defaults to 20.
- `paginationToken` (`string`, optional): Token for the next page, from the previous fullstory_segments_list response. Keep the other filters the same between pages.

Example input: `{}`

### `fullstory_session_events_get`

Get Session Events · Read-only

Get the full set of captured events for one Fullstory session, within seconds of capture. Needs an Architect or Admin API key.
Returns the session's raw events (navigations, clicks, inputs, errors, custom events and so on) with timestamps.
Use this to inspect exactly what happened in a session. Use fullstory_session_summary_generate for an AI summary instead.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `session_id` (`string`, required): The Fullstory session ID, URL-encoded as one path segment. Get it from fullstory_sessions_list or from the browser or mobile SDK's getSession call. Example: 4567890123456789:1234567890123456789.

Example input: `{"session_id":"<session_id>"}`

### `fullstory_sessions_list`

List Sessions · Read-only

List a user's most recent Fullstory sessions with their replay URLs, by uid or email, or fetch one session by your own session uid.
Returns sessions, each with its id, created_time and app_url (the replay link).
Use this to find session IDs and replay links. Use fullstory_session_events_get for what happened in a session.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, optional): The user's email address. Provide uid, email or session_uid. Example: daniel.falko@example.com.
- `limit` (`string`, optional): Maximum number of sessions to return, as a number. Defaults to 20. Example: 10.
- `session_uid` (`string`, optional): Your own session identifier, as set through the SDK or server API, to fetch one session. Do not combine with uid or email. Example: checkout-session-42.
- `uid` (`string`, optional): Your application's user ID (the value passed to FS('setIdentity')). Provide uid, email or session_uid; uid and email can be combined (results are the union). Example: xyz123.

Example input: `{}`

### `fullstory_summary_profile_get`

Get Summary Profile · Read-only

Get one session summary profile by ID.
Returns the profile's name and its slice, context, events, cache and LLM settings.
Use this to inspect a profile before generating summaries with it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The summary profile ID returned by fullstory_summary_profile_create or fullstory_summary_profiles_list. Example: my-checkout-summary.

Example input: `{"id":"<id>"}`

### `fullstory_summary_profiles_list`

List Summary Profiles · Read-only

List the session summary profiles (saved prompt and context settings) in Fullstory, one page at a time.
Returns the profiles with their ids, names and settings, plus next_page_token.
Use this to find a profile ID for fullstory_session_summary_generate.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `limit` (`integer`, optional): Maximum number of results to return, up to 100. Defaults to 20.
- `page_token` (`string`, optional): Token for the next page, from the next_page_token of the previous fullstory_summary_profiles_list response. Leave empty for the first page.

Example input: `{}`

### `fullstory_user_get`

Get User · Read-only

Get one Fullstory user by Fullstory user ID. Needs an Architect or Admin API key.
Returns the user's id, uid, display name, email, properties, deletion flag and app_url, plus the property schema when include_schema is true.
Use this when you have the Fullstory user ID. Use fullstory_users_list to find a user by uid, email or name.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The Fullstory-assigned user ID (the id returned by fullstory_user_create or fullstory_users_list), not your own uid. Example: 987654321.
- `include_schema` (`boolean`, optional): Set to true to include the property type schema in the response. Defaults to false.

Example input: `{"id":"<id>"}`

### `fullstory_users_batch_import_errors_list`

List User Batch Import Errors · Read-only

List the users that failed in a batch user import job, one page at a time.
Returns each failed user with an error code and message, the total record count and next_page_token.
Use this after fullstory_users_batch_import_get reports failures.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): The batch user import job ID returned by fullstory_users_batch_import_create. Example: MTI4NjYxNjM0MjM1NzQ0MzQ5OA.
- `page_token` (`string`, optional): Token for the next page, from the next_page_token of the previous fullstory_users_batch_import_errors_list response. Leave empty for the first page.

Example input: `{"job_id":"<job_id>"}`

### `fullstory_users_batch_import_get`

Get User Batch Import Status · Read-only

Get the status of a batch user import job.
Returns the job (id, status, created and finished times) and the counts of imported users and errors.
Use this to poll a job from fullstory_users_batch_import_create. Then use fullstory_users_batch_imports_list or fullstory_users_batch_import_errors_list for the results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): The batch user import job ID returned by fullstory_users_batch_import_create. Example: MTI4NjYxNjM0MjM1NzQ0MzQ5OA.

Example input: `{"job_id":"<job_id>"}`

### `fullstory_users_batch_imports_list`

List User Batch Import Results · Read-only

List the users imported successfully by a batch user import job, one page at a time.
Returns each imported user's Fullstory id and details, plus next_page_token.
Use this to map your uids to Fullstory user IDs after a batch import.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`string`, required): The batch user import job ID returned by fullstory_users_batch_import_create. Example: MTI4NjYxNjM0MjM1NzQ0MzQ5OA.
- `include_schema` (`boolean`, optional): Set to true to include the property type schema in the response. Defaults to false.
- `page_token` (`string`, optional): Token for the next page, from the next_page_token of the previous fullstory_users_batch_imports_list response. Leave empty for the first page.

Example input: `{"job_id":"<job_id>"}`

### `fullstory_users_list`

List Users · Read-only

List Fullstory users that match a uid, email, display name or identified state, one page at a time. Needs an Architect or Admin API key.
Returns matching users (id, uid, display name, email, properties, app_url) and next_page_token.
Use this to find a user's Fullstory ID. Use fullstory_user_get when you already have it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `display_name` (`string`, optional): Filter by display name. Example: Daniel Falko.
- `email` (`string`, optional): Filter by email address. Example: daniel.falko@example.com.
- `include_schema` (`boolean`, optional): Set to true to include the property type schema in the response. Defaults to false.
- `is_identified` (`boolean`, optional): Set to true for identified users only, or false for anonymous users only.
- `page_token` (`string`, optional): Token for the next page, from the next_page_token of the previous fullstory_users_list response. Leave empty for the first page.
- `uid` (`string`, optional): Filter by your application's user ID. Example: xyz123.

Example input: `{}`

### `fullstory_annotation_create`

Create Annotation · Write

Create an annotation that marks a moment or period, such as a release or campaign, on Fullstory charts.
Returns the annotation's text, start and end time and source.
Use this to mark deploys or incidents so they show on Fullstory metrics.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `text` (`string`, required): The annotation text, shown on charts. Example: Released checkout v2.
- `end_time` (`string`, optional): End of the annotation in ISO 8601. Defaults to the start time. Example: 2026-01-15T10:00:00Z.
- `source` (`string`, optional): Who or what created the annotation, shown in Fullstory. Example: Deploy bot.
- `start_time` (`string`, optional): Start of the annotation in ISO 8601. Defaults to now. Example: 2026-01-15T09:00:00Z.

Example input: `{"text":"<text>"}`

### `fullstory_event_create`

Create Event · Write

Send one custom server-side event to Fullstory for a user or session.
Returns an empty object on success.
Use this to record a backend action, such as a created ticket, on the user's timeline. Use fullstory_events_batch_import_create for many events.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name of the custom event. Example: Support Ticket Created.
- `context` (`object`, optional): Optional context the event happened in, with any of browser (url, user_agent, initial_referrer), mobile (app_id, app_version, app_name, build_variant), device (manufacturer, model, screen and viewport sizes) and location (country, region, city, latitude, longitude, ip_address). Example: {"browser": {"url": "https://www.example.com/checkout"}}.
- `idempotency_key` (`string`, optional): Optional unique key that makes the request idempotent: Fullstory returns the first result for repeated requests with the same key instead of acting twice. Example: 7b9c2f0e-4d1a-4a5e-9c3b-1f2e3d4c5b6a.
- `page_properties` (`object`, optional): Page-scoped properties copied onto every event on the same page, so pages can be searched by them. Example: {"page_type": "checkout"}.
- `page_properties_schema` (`object`, optional): Optional type declaration for page_properties, in the same shape as schema. Example: {"properties": {"page_type": "str"}}.
- `properties` (`object`, optional): Custom properties of the event as a JSON object. Example: {"ticket_id": "T-1001", "priority": "high"}.
- `schema` (`object`, optional): Optional type declaration that overrides Fullstory's type inference for the properties, as {"properties": {"<name>": "<type>"}} with types such as str, int, real, bool or date. Example: {"properties": {"total_spent": "real"}}.
- `session` (`object`, optional): Which session to attach the event to: {"id": ""}, {"uid": "<your session ID>"}, or {"use_most_recent": true} to use the user's session from the last 30 minutes (needs user). Leave out to record the event outside any session. Example: {"use_most_recent": true}.
- `timestamp` (`string`, optional): When the event happened, in ISO 8601. Defaults to when Fullstory receives it. Example: 2026-01-15T09:30:00Z.
- `user` (`object`, optional): Which user the event belongs to: {"uid": "<your user ID>"} or {"id": ""}. Leave out when session.id is given. Example: {"uid": "xyz123"}.

Example input: `{"name":"<name>"}`

### `fullstory_events_batch_import_create`

Create Event Batch Import · Write

Start a background job that imports many custom events into Fullstory at once.
Returns the job's id, status and creation time.
Use this for bulk or historical events, then poll fullstory_events_batch_import_get. Use fullstory_event_create for one event.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `requests` (`array`, required): Events to import. Each item takes the same fields as a single event: name (required), user, session, context, timestamp, properties and schema. Example: [{"name": "Support Ticket Created", "user": {"uid": "xyz123"}, "timestamp": "2026-01-15T09:30:00Z", "properties": {"ticket_id": "T-1001"}}].
- `idempotency_key` (`string`, optional): Optional unique key that makes the request idempotent: Fullstory returns the first result for repeated requests with the same key instead of acting twice. Example: 7b9c2f0e-4d1a-4a5e-9c3b-1f2e3d4c5b6a.

Example input: `{"requests":[{"name":"Support Ticket Created","user":{"uid":"xyz123"},"timestamp":"2026-01-15T09:30:00Z","properties":{"ticket_id":"T-1001"}}]}`

### `fullstory_segment_export_create`

Create Segment Export · Write

Schedule an export of a segment's users or events in JSON, NDJSON or CSV. Needs an Architect or Admin API key.
Returns the operationId of the export job.
Use this to pull data for a segment, then poll fullstory_operation_get and download with fullstory_search_export_results_get.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `format` (`string`, required): File format of the export. One of: `FORMAT_NDJSON`, `FORMAT_CSV`, `FORMAT_JSON`.
- `segmentId` (`string`, required): The segment to export, from fullstory_segments_list. Example: everyone.
- `timeRange` (`object`, required): Time range of the data to export, as {"start": "<RFC 3339>", "end": "<RFC 3339>"}. An empty start means the beginning of time and an empty end means now. Example: {"start": "2026-01-01T00:00:00Z", "end": "2026-01-31T23:59:59Z"}.
- `type` (`string`, required): TYPE_EVENT exports the events of the segment's sessions; TYPE_INDIVIDUAL exports the segment's users. One of: `TYPE_EVENT`, `TYPE_INDIVIDUAL`.
- `eventDetails` (`object`, optional): For TYPE_EVENT exports, which events to export relative to the segment's event filters: {"scope": "SCOPE_EVENTS"} (default), SCOPE_INDIVIDUALS, SCOPE_SESSIONS or SCOPE_PAGES.
- `fields` (`array`, optional): Fields to include; all fields when empty. Example: ["IndvId", "EventStart", "EventType"].
- `now` (`string`, optional): Pins the 'now' used for relative dates, in RFC 3339. Example: 2026-02-01T00:00:00Z.
- `segmentTimeRange` (`object`, optional): Optional time range that overrides the segment's own, in the same {start, end} shape. Example: {"start": "2026-01-01T00:00:00Z", "end": ""}.
- `timezone` (`string`, optional): IANA timezone for relative dates. Defaults to UTC. Example: America/New_York.

Example input: `{"format":"FORMAT_NDJSON","segmentId":"<segmentId>","timeRange":{"start":"2026-01-01T00:00:00Z","end":"2026-01-31T23:59:59Z"},"type":"TYPE_EVENT"}`

### `fullstory_session_summary_generate`

Generate Session Summary · Write

Generate an AI summary of one Fullstory session, optionally following a saved summary profile. Needs an Architect or Admin API key.
Returns the generated summary text, or JSON when the profile defines a response schema.
Use this to explain a session in words. Use fullstory_session_events_get for the raw events.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `session_id` (`string`, required): The Fullstory session ID, URL-encoded as one path segment. Get it from fullstory_sessions_list or from the browser or mobile SDK's getSession call. Example: 4567890123456789:1234567890123456789.
- `config_profile` (`string`, optional): ID of a summary profile from fullstory_summary_profile_create. Leave empty for a simple synopsis of the user's experience. Example: my-checkout-summary.
- `end_timestamp` (`string`, optional): Only include events before this time, in RFC 3339. Example: 2026-01-15T10:00:00Z.

Example input: `{"session_id":"<session_id>"}`

### `fullstory_summary_profile_create`

Create Summary Profile · Write

Create a session summary profile: the prompt text, LLM options and which session data Fullstory sends to the model.
Returns the new profile's id.
Use this once, then pass the id as config_profile to fullstory_session_summary_generate.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `cache` (`object`, optional): Cache options, such as {"enable_event_cache": true}.
- `context` (`object`, optional): Which session context to include: include or exclude lists of user, org, location and device. Example: {"exclude": ["location"]}.
- `events` (`object`, optional): Which events to include: include_types or exclude_types (for example navigate, click, rage-click, input-change), plus flags such as exclude_selectors and include_descriptions. Example: {"exclude_types": ["input-change"]}.
- `llm` (`object`, optional): Prompt and model options: pre_prompt (text before the session data), post_prompt (text after it), temperature, and an optional response_schema for JSON output. Example: {"pre_prompt": "Summarize where this user struggled during checkout.", "temperature": 0.2}.
- `name` (`string`, optional): Display name of the profile. Example: Checkout friction summary.
- `slice` (`object`, optional): Which part of the session to use: mode (FIRST or LAST), event_limit, duration_limit_ms, start_timestamp and end_timestamp. Example: {"mode": "LAST", "event_limit": 500}.

Example input: `{}`

### `fullstory_user_create`

Create or Update User · Write

Create a user in Fullstory, or update the identified user that already has the given uid (upsert).
Returns the Fullstory user id.
Use this to send user attributes from your backend. Use fullstory_user_update when you have the Fullstory user ID, and fullstory_users_batch_import_create for many users.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `display_name` (`string`, optional): The user's display name, up to 256 characters. Example: Daniel Falko.
- `email` (`string`, optional): The user's email address, up to 128 characters. Example: daniel.falko@example.com.
- `idempotency_key` (`string`, optional): Optional unique key that makes the request idempotent: Fullstory returns the first result for repeated requests with the same key instead of acting twice. Example: 7b9c2f0e-4d1a-4a5e-9c3b-1f2e3d4c5b6a.
- `properties` (`object`, optional): Custom properties for the user, as a JSON object. Up to 500 properties; names use letters, digits and underscores and start with a letter; values can be nested objects and up to 8 KB each. Example: {"pricing_plan": "paid", "total_spent": 14.55}.
- `schema` (`object`, optional): Optional type declaration that overrides Fullstory's type inference for the properties, as {"properties": {"<name>": "<type>"}} with types such as str, int, real, bool or date. Example: {"properties": {"total_spent": "real"}}.
- `uid` (`string`, optional): Your application's ID for the user, up to 256 characters. Once set it cannot be changed. Example: xyz123.

Example input: `{}`

### `fullstory_user_update`

Update User · Write

Update a Fullstory user's uid, display name, email or properties by Fullstory user ID. A uid that is already set cannot be changed.
Returns the user's Fullstory id.
Use this when you have the Fullstory user ID. Use fullstory_user_create to upsert by uid.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The Fullstory-assigned user ID (the id returned by fullstory_user_create or fullstory_users_list), not your own uid. Example: 987654321.
- `display_name` (`string`, optional): The user's display name, up to 256 characters. Example: Daniel Falko.
- `email` (`string`, optional): The user's email address, up to 128 characters. Example: daniel.falko@example.com.
- `properties` (`object`, optional): Custom properties for the user, as a JSON object. Up to 500 properties; names use letters, digits and underscores and start with a letter; values can be nested objects and up to 8 KB each. Example: {"pricing_plan": "paid", "total_spent": 14.55}.
- `schema` (`object`, optional): Optional type declaration that overrides Fullstory's type inference for the properties, as {"properties": {"<name>": "<type>"}} with types such as str, int, real, bool or date. Example: {"properties": {"total_spent": "real"}}.
- `uid` (`string`, optional): Your application's ID for the user, up to 256 characters. Once set it cannot be changed. Example: xyz123.

Example input: `{"id":"<id>"}`

### `fullstory_users_batch_import_create`

Create User Batch Import · Write

Start a background job that creates or updates many Fullstory users at once.
Returns the job's id, status and creation time.
Use this for bulk user imports, then poll fullstory_users_batch_import_get. Use fullstory_user_create for one user.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `requests` (`array`, required): Users to import. Each item takes the same fields as a single user: uid, display_name, email, properties and schema (or id to update an existing Fullstory user). Example: [{"uid": "xyz123", "email": "daniel.falko@example.com", "properties": {"pricing_plan": "paid"}}].
- `idempotency_key` (`string`, optional): Optional unique key that makes the request idempotent: Fullstory returns the first result for repeated requests with the same key instead of acting twice. Example: 7b9c2f0e-4d1a-4a5e-9c3b-1f2e3d4c5b6a.

Example input: `{"requests":[{"uid":"xyz123","email":"daniel.falko@example.com","properties":{"pricing_plan":"paid"}}]}`

### `fullstory_summary_profile_delete`

Delete Summary Profile · Destructive

Delete a session summary profile by ID.
Returns an empty object on success.
Use this to remove a profile you no longer use. This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The summary profile ID returned by fullstory_summary_profile_create or fullstory_summary_profiles_list. Example: my-checkout-summary.

Example input: `{"id":"<id>"}`

### `fullstory_user_delete`

Delete User · Destructive

Permanently delete a Fullstory user and their captured data by Fullstory user ID. Deletion runs in the background. Needs an Architect or Admin API key.
Returns an empty object; the deletion finishes in the background and shows up as a DELETE_USER operation in fullstory_operations_list.
Use this for data deletion requests. This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The Fullstory-assigned user ID (the id returned by fullstory_user_create or fullstory_users_list), not your own uid. Example: 987654321.

Example input: `{"id":"<id>"}`

## Related

Other Analytics connectors ([all 176](/agentkit/connectors/?category=analytics)):

- [Microsoft 365](/agentkit/connectors/microsoft365/): Scalekit connector, OAuth, 317 tools
- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Snowflake](/agentkit/connectors/snowflake/): Scalekit connector, OAuth, 42 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
