How to connect Windsor.ai to Hermes Agent
Connect Windsor.ai to Hermes 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, Hermes Agent can read and act on Windsor.ai from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Windsor.ai 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 Windsor.ai setup: pair once in the browser and your always-on Hermes agent can act on Windsor.ai 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 Windsor.ai.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Windsor.ai
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Windsor.ai?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Windsor.ai in the ClawLink dashboard — paste your Windsor.ai API key once.
Verify the connection by asking Hermes:
List the relevant items in Windsor.ai, group them by priority, and recommend what Hermes should do next.
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:
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 Hermes
Looking for a Windsor.ai MCP server for Hermes Agent? ClawLink connects Windsor.ai to Hermes Agent and exposes 6 Windsor.ai tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Windsor.ai integration works the same way.
What the Hermes Agent Windsor.ai integration can do
6 Windsor.ai tools are ready for Hermes Agent once the account is connected.
All 6 Windsor.ai tools for Hermes
| 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 Hermes 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 Hermes should do next.
List the relevant items in Windsor.ai, group them by priority, and recommend what Hermes should do next.
List the relevant items in Windsor.ai, group them by priority, and recommend what Hermes should do next.
List the relevant items in Windsor.ai, group them by priority, and recommend what Hermes 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 Hermes Agent. 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 Hermes Agent 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
Hermes paired but still can't use Windsor.ai
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 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 Hermes Agent Windsor.ai integration?
Yes. ClawLink is the fastest way to connect Hermes to Windsor.ai: link your Windsor.ai account once in the browser and Hermes Agent can call the Windsor.ai API through 6 ready-made tools — no custom code or token handling.
How do I connect Windsor.ai 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 Windsor.ai in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Windsor.ai in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Windsor.ai working from chat.
Hermes paired but still can't use Windsor.ai
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
Hermes PostHog integration
Track user behavior and feature flags
Hermes DataforSEO integration
SEO data APIs for keywords, SERP, and site audits
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.