# How to connect Klipfolio to Hermes Agent (paste one key, 50 tools) > Connect Klipfolio to Hermes with ClawLink: paste your Klipfolio key once and 50 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/klipfolio Most guides for giving Hermes Agent Klipfolio 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 Klipfolio setup: pair once in the browser and your always-on Hermes agent can act on Klipfolio 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 Klipfolio. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Klipfolio** — 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 klipfolio # connect Klipfolio (browser OAuth) npx -y @useclawlink/cli actions klipfolio # list available actions npx -y @useclawlink/cli run klipfolio --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 Klipfolio in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Klipfolio API key once. Verify the connection by asking Hermes: > Pull the relevant data from Klipfolio, 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 Klipfolio is connected in the dashboard, that agent calls the same 50 Klipfolio 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). ## Klipfolio MCP for Hermes Looking for a Klipfolio MCP server for Hermes Agent? ClawLink connects Klipfolio to Hermes Agent and exposes 50 Klipfolio 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 Klipfolio integration](https://claw-link.dev/openclaw/klipfolio) works the same way. ## What the Hermes Agent Klipfolio integration can do 50 Klipfolio tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 50. ### 30 of 50 Klipfolio tools for Hermes | Tool | What it does | |---|---| | **Get dashboard** `klipfolio_get_dashboard` | Retrieves detailed information about a specific dashboard (formerly known as tab) in Klipfolio | | **Get data source** `klipfolio_get_data_source` | Retrieve detailed information about a specific data source in Klipfolio | | **Get data source instance data** `klipfolio_get_data_source_instance_data` | Retrieve the actual data from a specific data source instance in Klipfolio | | **Get data source instance properties** `klipfolio_get_data_source_instance_properties` | Retrieve configuration properties for a specific data source instance in Klipfolio | | **Get data source instance2** `klipfolio_get_data_source_instance2` | Retrieve detailed information about a specific data source instance in Klipfolio | | **Get data source properties** `klipfolio_get_data_source_properties` | Retrieve properties for a specific data source in Klipfolio by its ID | | **Get data source share rights** `klipfolio_get_data_source_share_rights` | Retrieve sharing permissions for a specific data source in Klipfolio | | **Get group** `klipfolio_get_group` | Retrieve detailed information about a specific group in Klipfolio | | **Get group default tabs** `klipfolio_get_group_default_tabs` | Retrieve the list of default tabs (dashboards) for a specific group | | **Get group users** `klipfolio_get_group_users` | Retrieve all users belonging to a specific group in Klipfolio | | **Get klips** `klipfolio_get_klips` | Retrieves a list of all Klips accessible to the authenticated user | | **Get profile** `klipfolio_get_profile` | Retrieve the authenticated user's profile information and test the authentication status | | **Get role** `klipfolio_get_role` | Retrieve detailed information about a specific role in Klipfolio | | **Get role permissions** `klipfolio_get_role_permissions` | Retrieve the list of permissions assigned to a specific role in Klipfolio | | **Get role users** `klipfolio_get_role_users` | Retrieve all users associated with a specific role in Klipfolio | | **Get user** `klipfolio_get_user` | Retrieve detailed information about a specific user in Klipfolio | | **Get user groups** `klipfolio_get_user_groups` | Retrieve all groups that a specific user belongs to in Klipfolio | | **Get user properties** `klipfolio_get_user_properties` | Retrieve custom properties associated with a specific user in Klipfolio | | **Get user roles** `klipfolio_get_user_roles` | Retrieve all roles assigned to a specific user in Klipfolio | | **Get user tab instances** `klipfolio_get_user_tab_instances` | Retrieve all tab instances associated with a specific user | | **List data source instances** `klipfolio_list_data_source_instances` | Retrieve all data source instances accessible to the authenticated user | | **List data sources** `klipfolio_list_data_sources` | Retrieves a list of all data sources associated with an authenticated Klipfolio account | | **List groups** `klipfolio_list_groups` | Retrieve all groups from a Klipfolio account | | **List roles** `klipfolio_list_roles` | Retrieve all roles in the company | | **List users** `klipfolio_list_users` | Retrieve all users in the company | | **Assign user role** `klipfolio_assign_user_role` | Assign a role to a user in Klipfolio | | **Create data source** `klipfolio_create_data_source` | Creates a new data source in Klipfolio | | **Create data source instance** `klipfolio_create_data_source_instance` | Create a new data source instance based on an existing data source in Klipfolio | | **Create group** `klipfolio_create_group` | Create a new group in Klipfolio | | **Create role** `klipfolio_create_role` | Create a new role in Klipfolio with optional permissions | ## Example prompts **Get Dashboard** > Pull the relevant data from Klipfolio, summarize it in plain English, and point out anything that needs attention. **Get Data Source** > Pull the relevant data from Klipfolio, summarize it in plain English, and point out anything that needs attention. **Get Data Source Instance Data** > Pull the relevant data from Klipfolio, summarize it in plain English, and point out anything that needs attention. **Get Data Source Instance Properties** > Pull the relevant data from Klipfolio, 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 Klipfolio working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Klipfolio API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Klipfolio 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 Klipfolio. | 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 Klipfolio actions to the runtime in a format your agent can reliably use. | 50 tools for Klipfolio are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Klipfolio 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 Klipfolio in the browser, and the 50 tools above work from chat. There is no SDK and no config file, and the Klipfolio 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 Klipfolio 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 Klipfolio 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 Klipfolio tools Klipfolio 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 Klipfolio 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. ### Klipfolio 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 Klipfolio 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 Klipfolio integration? Yes. ClawLink is the fastest way to connect Hermes to Klipfolio: link your Klipfolio account once in the browser and Hermes Agent can call the Klipfolio API through 50 ready-made tools — no custom code or token handling. ### How do I connect Klipfolio 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 Klipfolio in the dashboard and Hermes can use it from the next message — no config files, and the Klipfolio key you paste is stored server-side instead of in your environment. ### How long does it take to connect Klipfolio to Hermes Agent? About two minutes. Sign in, click Connect next to Klipfolio in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Klipfolio 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 Klipfolio working from chat. ### Hermes paired but still can't use Klipfolio 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](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [DataforSEO tools](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Hermes Metabase integration](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.