Integration · Analytics and data
AI agents for Fullstory
Find Fullstory users and their session replays, get an AI summary of what happened in a session, set user properties, send server-side events, list segments, and delete a user, with an API key.
- Actions
- 9
- Read
- 5
- Write
- 4
Actions
What your agents can do in Fullstory
9 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 5
Look things up. Nothing changes.
Find users
Finds users by your own user ID (uid), email or display name, or lists identified or anonymous users, as results.
Get a user
Reads one user by Fullstory's user ID: uid, display_name, email, custom properties and app_url.
List a user's session replays
Lists up to limit most recent sessions of a user, found by your uid or by email, as results: each with its id, created_time and app_url (the replay link).
Summarize a session
Returns Fullstory's AI summary of one session in summary: what the person did, where they struggled and what errors they hit.
List segments
Lists the saved segments, as segments: each with id, name, creator (an email), created and url; nextPaginationToken pages on.
Write 4
Create, change or send.
Create or update a user
Creates a user, or updates the one with the same uid, with a display name, email and custom properties like {"pricing_plan".
Update a user
Changes one user, by Fullstory's user ID: display name, email or custom properties (merged with the ones it has).
Send an event
Records a custom event from your server, like "Subscription Renewed" with properties {"plan": "pro", "amount": 99}, for a user given by your uid or Fullstory's user_id.
Delete a userDeletes data
Deletes one user and all of their sessions and events from Fullstory, by Fullstory's user ID (for a privacy request).
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Fullstory account.
What you enter
- API key
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Fullstory data
Ask a question in plain words. The agent can find users, get a user or list a user's session replays in Fullstory, then answers with what it found.
- 02
Let an agent update Fullstory
Have the agent create or update a user or update a user in Fullstory as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Fullstory and Slack: it can find users in Fullstory and post a summary to a Slack channel in the same run.
FAQ
Fullstory and MyDeepAgents
Can MyDeepAgents connect to Fullstory?
Yes. The Fullstory connector has 9 actions: 5 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Fullstory?
Paste an API key from your Fullstory account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Fullstory without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Fullstory in workflows as well as agents?
Yes. Every Fullstory action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Fullstory to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.