# How to connect FullStory to Hermes Agent (paste one key, 30 tools) > Connect FullStory to Hermes with ClawLink: paste your FullStory key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/fullstory Most guides for giving Hermes Agent FullStory access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical FullStory setup: pair once in the browser and your always-on Hermes agent can act on FullStory for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to FullStory. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect FullStory** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect fullstory # connect FullStory (browser OAuth) npx -y @useclawlink/cli actions fullstory # list available actions npx -y @useclawlink/cli run fullstory --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect FullStory in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your FullStory API key once. Verify the connection by asking Hermes: > Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## FullStory MCP for Hermes Looking for a FullStory MCP server for Hermes Agent? ClawLink connects FullStory to Hermes Agent and exposes 30 FullStory tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw FullStory integration](https://claw-link.dev/openclaw/fullstory) works the same way. ## What the Hermes Agent FullStory integration can do 30 FullStory tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Get Account** > Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention. **Get Element Block** > Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention. **Get Extraction Rule** > Pull the relevant data from FullStory, summarize it in plain English, and point out anything that needs attention. **Get Import Status** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use FullStory Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent FullStory integration? Yes. ClawLink is the fastest way to connect Hermes to FullStory: link your FullStory account once in the browser and Hermes Agent can call the FullStory API through 30 ready-made tools — no custom code or token handling. ### How do I connect FullStory to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect FullStory in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to FullStory in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want FullStory working from chat. ### Hermes paired but still can't use FullStory Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [PostHog tools](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [Hermes DataforSEO integration](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Metabase](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.