- Home
- Resources
- Integrations
- Fullstory
Claude Fullstory connectorWhat Claude can do in your Fullstory account.
The Claude Fullstory connector exposes 29 tools. 21 read, 8 write, 0 left undocumented. Claude turns plain questions into segments, metrics, funnels and journeys, then opens the real sessions behind the numbers. Here: what it saves, what it cannot touch, and what admins must switch on.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for product and UX teams
Fullstory already records how people use your product. The connector lets you question that data in plain language: Claude defines the cohort, computes the number, explains it, and then opens actual user sessions so a drop in conversion comes with the reason, not just the percentage.
Find where checkout leaks. A product manager describes the purchase path in a sentence. build_funnel saves it as a funnel, compute_funnel returns conversion at every step, and get_funnel_sessions lists the sessions that dropped at the worst one.
Check whether yesterday's release broke something. discover_groups scans for frustration signals such as errors and rage clicks and can compare with the previous period to surface regressions, then get_opportunity_stats sizes the one that matters.
Let Claude watch the replay for you. get_session_events fetches a session's full event transcript, and session_screenshot shows what the user saw at a given moment.
What it cannot do: Fullstory's limits page rules out dashboards, heatmaps, privacy rules, user management, billing and settings. Tables stop at 50 rows and session lists at 50 sessions, so it is not an export tool. Nothing runs on its own either: no alert fires when a metric dips overnight. That kind of watch belongs to an automation tool, a different job gathered on our Integrations page. To turn findings into tickets in the same chat, the Claude asana connector can sit next to this one.
The vocabulary in one minute
Five words you will meet while connecting Fullstory.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the tools it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use afterwards. Given once per person and revocable.
- Approval
- The confirmation Claude waits for before doing something that changes your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Fullstory.
Plug Fullstory into Claude in three steps
- 01
Find Fullstory in Claude
In Claude's settings, open Customize, then Connectors, and find Fullstory in the list. On a Team or Enterprise workspace, an Owner or Primary Owner must enable the connector first; each member then signs in individually.
- 02
Start the connection
Click Connect on its row, then sign in to Fullstory in the window that Fullstory opens itself. If the link ever breaks, use Disconnect and connect again.
- 03
Read the authorization screen
Read Fullstory's authorization screen before you accept. It belongs to Fullstory, not to Claude, and it decides what the access covers. Then ask Claude which Fullstory tools it can see to confirm.
The 29 tools, sorted by what they do
Fullstory gives Claude 29 tools: 21 that read your account, 8 that change something in it.
Twenty-one tools read or inspect, eight save definitions in your Fullstory account. Names stay in English, exactly as Claude shows them.
- 21 read
- 8 write
Tools index
- compute_funnel
- compute_journey
- compute_metric
- discover_groups
- discover_org_context
- get_funnel
- get_funnel_sessions
- get_journey
- get_metric
- get_opportunity_stats
- get_segment
- get_session_events
- get_sessions
- get_sessions_for_opportunity
- get_view_counts
- session_close
- session_diff
- session_get_a11y_tree
- session_open
- session_screenshot
- session_view
What Claude reads (21)
21 toolsTwenty-one tools that compute, look up or replay without touching your saved objects.
compute_funnel
Runs a saved funnel and returns the count at each step, the conversion from the previous step and the conversion from the first one.
compute_journey
Executes a journey and gives its step-by-step breakdown around the pivot event, showing the events users reached at each step outward and the most common end-to-end paths.
compute_metric
Executes a metric definition against your data, optionally scoped to a segment and a time range, and returns a count, a table or a trend with a link to Fullstory.
discover_groups
Surfaces the leading frustration signals across your product, querying the whole org when no scope is set, and can compare with a prior period to reveal regressions.
discover_org_context
Searches the objects your org has configured, such as pages, named elements, defined and custom events and custom variables, so Claude resolves the right IDs before building anything.
get_funnel
Retrieves saved funnels by ID or by name pattern, with their step count and a readable description, and can be limited to the funnels you own.
get_funnel_sessions
Lists sessions for one step of a funnel, either the people who completed it or those who dropped off there, each with a direct replay link.
get_journey
Retrieves saved journeys by ID or name pattern, each with a plain-English description of its direction, pivot step, audience and time window, and can be limited to the ones you own.
get_metric
Looks up one or more saved metrics by ID or name pattern and returns their names with a readable description of each definition.
get_opportunity_stats
Computes live statistics for one frustration signal: how many users it affects, which pages, domains and devices, and how fast it is growing or shrinking.
get_segment
Retrieves one or more saved segments by ID or name pattern, with a human-readable description of who falls into each.
get_session_events
Fetches a complete, chronological record of everything in a session: clicks, navigations, errors, network requests and more, which Claude can read end to end.
get_sessions
Returns sessions that match a metric or a segment, each with a direct replay link, turning an aggregate into concrete user evidence.
get_sessions_for_opportunity
Pulls real sessions where a specific frustration signal was observed, so Claude can read what those users were trying to do at the time.
get_view_counts
Counts how often saved segments or metrics were viewed, for up to 10 items of one kind, over a lookback of 30 days by default and 90 at most.
session_close
Ends a visual inspection session and frees what it held on Fullstory's side. Fullstory marks it as required after every opened replay, or further openings may be blocked.
session_diff
Compares the page structure of an open session between two timestamps and returns a text summary of the differences.
session_get_a11y_tree
Returns the accessibility tree of an open session at a given page and timestamp, with roles, labels and hierarchy, so Claude can tell which element was actually clicked.
session_open
Opens a Fullstory session for visual inspection from the IDs in its replay URL and returns event summaries that help pick the interesting moments.
session_screenshot
Renders what the user saw in an open session at a given page and timestamp, which is how Claude sees the exact moment you care about.
session_view
Fullstory lists this tool as deprecated: it no longer works and only returns a message pointing to the screenshot and page-structure tools that replaced it.
What Claude saves (8)
8 toolsEight tools that save segments, metrics, funnels or journeys in Fullstory. No source gives them their own confirmation: the general rule below applies.
build_funnel
Approval: see the ruleTurns a plain description of ordered user actions into a funnel and saves it in Fullstory, with a link to open it there. It also returns the new funnel's ID.
build_journey
Approval: see the ruleConverts a description of an anchor event and a direction into a journey and saves it, returning a link to Fullstory.
build_metric
Approval: see the ruleConverts a question into a metric definition, as a single number, a top list or a trend. Fullstory's directory sheet says Claude creates the metric in Fullstory so the team can reuse it.
build_segment
Approval: see the ruleTurns a description of users or behaviour into a Fullstory segment, saves it and returns its ID with a link.
update_funnel
Approval: see the ruleAdjusts a saved funnel's time window, aggregation, steps or conversion window and saves the result under a new ID, leaving the original funnel as it was.
update_journey
Approval: see the ruleModifies a saved journey's time window, direction, attached segment or diagram settings, and saves a new version while the source stays unchanged.
update_metric
Approval: see the ruleEdits an existing metric definition from a plain instruction, such as counting unique users instead of events, and returns a new metric ID.
update_segment
Approval: see the ruleUpdates a saved segment from a plain instruction, for example adding iOS users only or removing a checkout filter, and saves it under a new segment ID.
What Claude asks before acting
By default, Claude stops and asks for your confirmation before every action it takes on an account on your behalf. Here that concerns eight tools, the ones that save segments, metrics, funnels and journeys in your Fullstory.
On Team and Enterprise, workspace owners decide whether members may let some actions through without a prompt, and they can restrict what a connector does for the whole organisation, for example keeping reads and closing writes. Nobody overrides that from their own account. Claude works with your Fullstory access and nothing beyond it, and each connection covers a single Fullstory org, never several at once.
Which plans include it
Of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is published nowhere, a genuine gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organisation before members can connect. On the Fullstory side, StoryAI and the protocol toggle must both be enabled for your org. The connector's sheet in the official directory shows its current state.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing runs by itself when a metric drops or a new error appears.
The eight saving tools are what the sheet exposes today, and an admin can open more actions than any public sheet lists. The directory's partner badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools. Everything here comes from Fullstory's developer documentation, still marked beta; neither Claude's help centre nor Anthropic's developer docs cover this connector. And two Fullstory pages do not describe writing the same way, as shown below.
Can the Fullstory connector write to your account?
- Fullstory, Limits & What's Not Supported Yet ↗undated on the pageHeaded "write operations not supported": no dashboards, no privacy rule changes, no user management through the connector.
- Fullstory, Tools Reference ↗undated on the pageDescribes tools that persist segments and funnels, save journeys and return new IDs when definitions are refined.
What this page followsBoth pages come from Fullstory and neither carries a date, so neither is out of date on paper. Read together, the tool list is the more precise one: Claude does save segments, metrics, funnels and journeys, but it does not create dashboards, touch privacy rules or manage users. The blanket "no writes" heading is simply too broad.
Need help connecting Fullstory to Claude?
A person reads every message.
