How to connect Windsor.ai to OpenClaw
Connect Windsor.ai to OpenClaw with ClawLink: paste your Windsor.ai key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
Windsor.aiAPI KEYMCPWindsor.ai connects marketing and business data sources for analytics, reporting, account management, and supported write actions.. Once connected, OpenClaw can read and act on Windsor.ai from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Windsor.ai 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 Windsor.ai setup: install one ClawHub skill, connect Windsor.ai in the browser, and OpenClaw can call real Windsor.ai 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 Windsor.ai.
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 Windsor.ai
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Windsor.ai?"
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 Windsor.ai in the ClawLink dashboard — paste your Windsor.ai API key once.
Verify the connection by asking OpenClaw:
List the relevant items in Windsor.ai, group them by priority, and recommend what OpenClaw should do next.
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 Windsor.ai is connected in the dashboard, that agent calls the same 6 Windsor.ai tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Windsor.ai MCP for OpenClaw
Looking for a Windsor.ai MCP server for OpenClaw? ClawLink connects Windsor.ai to OpenClaw and exposes 6 Windsor.ai tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Windsor.ai integration works the same way.
What the OpenClaw Windsor.ai integration can do
6 Windsor.ai tools are ready for OpenClaw once the account is connected.
All 6 Windsor.ai tools for OpenClaw
| Tool | What it does |
|---|---|
List co user linked accounts windsor_ai_list_co_user_linked_accounts | List source accounts connected through Windsor.ai co-user authorization links, optionally |
List connector actions windsor_ai_list_connector_actions | Discover Windsor.ai write-action IDs and parameter schemas without executing them |
List connector fields windsor_ai_list_connector_fields | List queryable field IDs for one specific Windsor.ai connector |
List connector options windsor_ai_list_connector_options | List connector-specific query options for one connected Windsor.ai source |
List connectors windsor_ai_list_connectors | List Windsor.ai connector IDs that can be used with discovery, data-query, and |
Query connector data windsor_ai_query_connector_data | Query a selected Windsor.ai connector, or 'all' for blended data, using explicit fields and |
Try it: find the Windsor.ai tool you need
Browse the 6 Windsor.ai tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
List the relevant items in Windsor.ai, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Windsor.ai, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Windsor.ai, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Windsor.ai, group them by priority, and recommend what OpenClaw should do next.
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 Windsor.ai working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Windsor.ai API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Windsor.ai 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 Windsor.ai. | 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 Windsor.ai actions to the runtime in a format your agent can reliably use. | 6 tools for Windsor.ai are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Windsor.ai 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 Windsor.ai in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Windsor.ai 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 Windsor.ai skill but can't call the tools
The ClawHub skill teaches OpenClaw about Windsor.ai, but the calls run through the ClawLink plugin and your connected account. Make sure Windsor.ai 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 Windsor.ai 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 Windsor.ai tools
Windsor.ai 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 Windsor.ai 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.
Windsor.ai 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 Windsor.ai 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 Windsor.ai integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Windsor.ai: link your Windsor.ai account once in the browser and OpenClaw can call the Windsor.ai API through 6 ready-made tools — no custom code or token handling.
How do I add Windsor.ai to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Windsor.ai skill from ClawHub, then you click Connect in the dashboard to authorize Windsor.ai. OpenClaw calls the tools from the next message — no config files, and the Windsor.ai key you paste is stored server-side instead of in your environment.
How long does it take to connect Windsor.ai to OpenClaw?
About two minutes. Sign in, click Connect next to Windsor.ai in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Windsor.ai 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 Windsor.ai working from chat.
OpenClaw installed the Windsor.ai skill but can't call the tools
The ClawHub skill teaches OpenClaw about Windsor.ai, but the calls run through the ClawLink plugin and your connected account. Make sure Windsor.ai 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.
