How to connect FullStory to OpenClaw
Connect FullStory to OpenClaw with ClawLink: paste your FullStory key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine.
FullStoryAPI KEYMCPFullStory provides digital experience analytics APIs for managing users, events, sessions, exports, recording settings, privacy rules, and related organization data.. Once connected, OpenClaw can read and act on FullStory from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to FullStory access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical FullStory setup: install one ClawHub skill, connect FullStory in the browser, and OpenClaw can call real FullStory actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to FullStory.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect FullStory
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with FullStory?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect FullStory in the ClawLink dashboard — paste your FullStory API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once FullStory is connected in the dashboard, that agent calls the same 30 FullStory tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
FullStory MCP for OpenClaw
Looking for a FullStory MCP server for OpenClaw? ClawLink connects FullStory to OpenClaw and exposes 30 FullStory tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes FullStory integration works the same way.
What the OpenClaw FullStory integration can do
30 FullStory tools are ready for OpenClaw once the account is connected. The 28 below are the ones people reach for most; your agent can call all 30.
28 of 30 FullStory tools for OpenClaw
| Tool | What it does |
|---|---|
Get account fullstory_get_account | Validate the connected API key and return its FullStory organization, identity, and API-key role |
Get element block fullstory_get_element_block | Get one FullStory privacy element-block rule by ID, including its exact selector source |
Get extraction rule fullstory_get_extraction_rule | Get one FullStory beta extraction rule by ID, including its archive state and complete nested |
Get import status fullstory_get_import_status | Get status and success/error counts for an asynchronous FullStory event or user import job |
Get operation fullstory_get_operation | Get detailed status, progress, operation-specific results, and failure details for one |
Get organization quotas fullstory_get_organization_quotas | Return current FullStory session and server-event quota usage, limits, and quota periods |
Get recording settings fullstory_get_recording_settings | Get one current FullStory recording-settings category |
Get segment fullstory_get_segment | Get metadata and the FullStory app URL for one segment |
Get user fullstory_get_user | Retrieve one user by FullStory-generated user ID, including profile fields and a FullStory app |
List datasets fullstory_list_datasets | List beta datasets readable by the connected FullStory organization |
List element blocks fullstory_list_element_blocks | Return one page of custom and built-in FullStory privacy element-block rules |
List extraction rules fullstory_list_extraction_rules | List all FullStory beta extraction rules matching one required scope and optional filters |
List import records fullstory_list_import_records | Return one page of successful or failed records from a FullStory event or user import job |
List operations fullstory_list_operations | Return one page of asynchronous FullStory operations, optionally filtered by state or type |
List recording settings history fullstory_list_recording_settings_history | Return one page of historical FullStory recording settings for blocking, domain, geo, privacy |
List segments fullstory_list_segments | Return one page of FullStory segments, optionally filtered by creator |
List sessions fullstory_list_sessions | Find recent FullStory session replay links by application UID, email, or exact session UID |
Search users fullstory_search_users | Find FullStory users by UID, email, display name, or identification state |
Create annotation fullstory_create_annotation | Add a persistent annotation to the FullStory timeline for a point or time range |
Create element block fullstory_create_element_block | Create a beta FullStory element recording or masking rule |
Create extraction rule fullstory_create_extraction_rule | Create and immediately activate one FullStory beta extraction rule using the provider's nested |
Import events fullstory_import_events | Start an asynchronous import of 1 to 50,000 server events |
Import users fullstory_import_users | Start an asynchronous upsert import of 1 to 50,000 users |
Upsert user fullstory_upsert_user | Create or update one FullStory user |
Cancel operation fullstory_cancel_operation | Irreversibly request cancellation of a cancelable in-progress FullStory operation, currently |
Set extraction rule archived fullstory_set_extraction_rule_archived | Archive a FullStory beta extraction rule to stop future capture, or unarchive it to resume |
Update element block fullstory_update_element_block | Fully replace an editable beta FullStory element recording or masking rule |
Update extraction rule fullstory_update_extraction_rule | Partially update a FullStory beta extraction rule using last-write-wins semantics |
Try it: find the FullStory tool you need
Browse the 28 FullStory tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want FullStory working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the FullStory API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected FullStory account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for FullStory. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right FullStory actions to the runtime in a format your agent can reliably use. | 30 tools for FullStory are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes FullStory to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect FullStory in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the FullStory key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the FullStory skill but can't call the tools
The ClawHub skill teaches OpenClaw about FullStory, but the calls run through the ClawLink plugin and your connected account. Make sure FullStory is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect FullStory from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling FullStory tools
FullStory tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every FullStory call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
FullStory returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for FullStory has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw FullStory integration?
Yes. ClawLink is the fastest way to connect OpenClaw to FullStory: link your FullStory account once in the browser and OpenClaw can call the FullStory API through 30 ready-made tools — no custom code or token handling.
How do I add FullStory to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink FullStory skill from ClawHub, then you click Connect in the dashboard to authorize FullStory. OpenClaw calls the tools from the next message — no config files, and the FullStory key you paste is stored server-side instead of in your environment.
How long does it take to connect FullStory to OpenClaw?
About two minutes. Sign in, click Connect next to FullStory in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring FullStory up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want FullStory working from chat.
OpenClaw installed the FullStory skill but can't call the tools
The ClawHub skill teaches OpenClaw about FullStory, but the calls run through the ClawLink plugin and your connected account. Make sure FullStory is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
