# How to connect Wistia to OpenClaw (paste one key, 10 tools) > Connect Wistia to OpenClaw with ClawLink: paste your Wistia key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/wistia The usual route to Wistia 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 Wistia setup: install one ClawHub skill, connect Wistia in the browser, and OpenClaw can call real Wistia 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 Wistia. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Wistia** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 wistia # connect Wistia (browser OAuth) npx -y @useclawlink/cli actions wistia # list available actions npx -y @useclawlink/cli run wistia --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Wistia in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Wistia API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Wistia, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Wistia is connected in the dashboard, that agent calls the same 10 Wistia 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). ## Wistia MCP for OpenClaw Looking for a Wistia MCP server for OpenClaw? ClawLink connects Wistia to OpenClaw and exposes 10 Wistia 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 Hermes instead? The [Hermes Wistia integration](https://claw-link.dev/hermes/wistia) works the same way. ## What the OpenClaw Wistia integration can do 10 Wistia tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 10. ### 8 of 10 Wistia tools for OpenClaw | Tool | What it does | |---|---| | **Get analytics summary** `wistia_get_analytics_summary` | Return account-wide or single-media Wistia performance metrics for an inclusive start date and | | **Get media** `wistia_get_media` | Return detailed metadata, assets, folder placement, tags, and processing state for one Wistia | | **Search content** `wistia_search_content` | Search the connected Wistia account for media, folders, subfolders, channels, and channel | | **Create folder** `wistia_create_folder` | Create a Wistia folder for organizing media, optionally make it public, and optionally set the | | **Import media from URL** `wistia_import_media_from_url` | Start importing a publicly reachable media URL into Wistia, optionally into a folder | | **Update folder** `wistia_update_folder` | Update a Wistia folder's name, description, public visibility, or anonymous transfer settings | | **Update media** `wistia_update_media` | Update a Wistia media item's name, description, tags, or still image reference | | **Set media archived state** `wistia_set_media_archived_state` | Archive one or more media items, or restore archived media into a destination folder, and wait | ## Example prompts **Get Analytics Summary** > Pull the relevant data from Wistia, summarize it in plain English, and point out anything that needs attention. **Get Media** > Pull the relevant data from Wistia, summarize it in plain English, and point out anything that needs attention. **Search Content** > Search Wistia for what I need, summarize the results, and tell me the next best action. **Create Folder** > Create it in Wistia for me, then confirm the important fields before you finish. ## 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 Wistia working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Wistia API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Wistia 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 Wistia. | 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 Wistia actions to the runtime in a format your agent can reliably use. | 10 tools for Wistia are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Wistia 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 Wistia in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Wistia 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. ### OpenClaw installed the Wistia skill but can't call the tools The ClawHub skill teaches OpenClaw about Wistia, but the calls run through the ClawLink plugin and your connected account. Make sure Wistia 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 Wistia 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 Wistia tools Wistia 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 Wistia 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. ### Wistia 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 Wistia has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Wistia integration? Yes. ClawLink is the fastest way to connect OpenClaw to Wistia: link your Wistia account once in the browser and OpenClaw can call the Wistia API through 10 ready-made tools — no custom code or token handling. ### How do I add Wistia to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Wistia skill from ClawHub, then you click Connect in the dashboard to authorize Wistia. OpenClaw calls the tools from the next message — no config files, and the Wistia key you paste is stored server-side instead of in your environment. ### How long does it take to connect Wistia to OpenClaw? About two minutes. Sign in, click Connect next to Wistia in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Wistia 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 Wistia working from chat. ### OpenClaw installed the Wistia skill but can't call the tools The ClawHub skill teaches OpenClaw about Wistia, but the calls run through the ClawLink plugin and your connected account. Make sure Wistia 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. ## Related - [Connect PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [OpenClaw Metabase integration](https://claw-link.dev/openclaw/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.