# How to connect Planly to Hermes Agent (paste one key, 15 tools) > Connect Planly to Hermes with ClawLink: paste your Planly key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/planly Most guides for giving Hermes Agent Planly 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 Planly setup: pair once in the browser and your always-on Hermes agent can act on Planly 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 Planly. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Planly** — 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 planly # connect Planly (browser OAuth) npx -y @useclawlink/cli actions planly # list available actions npx -y @useclawlink/cli run planly --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 Planly in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Planly API key once. Verify the connection by asking Hermes: > Use Planly to complete ai prompt and walk me through the result in plain English. ### 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 Planly is connected in the dashboard, that agent calls the same 15 Planly 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). ## Planly MCP for Hermes Looking for a Planly MCP server for Hermes Agent? ClawLink connects Planly to Hermes Agent and exposes 15 Planly 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 Planly integration](https://claw-link.dev/openclaw/planly) works the same way. ## What the Hermes Agent Planly integration can do 15 Planly tools are ready for Hermes Agent once the account is connected. The 13 below are the ones people reach for most; your agent can call all 15. ### 13 of 15 Planly tools for Hermes | Tool | What it does | |---|---| | **Complete AI prompt** `planly_complete_ai_prompt` | Complete a text prompt using AI | | **Get AI credits** `planly_get_ai_credits` | Retrieve available AI credits left in a team | | **Get team** `planly_get_team` | Retrieve detailed information about a specific team including permissions, limits, and | | **List channels** `planly_list_channels` | List all social media channels connected to a team | | **List media** `planly_list_media` | Retrieve a paginated list of media files in a team | | **List schedule groups** `planly_list_schedule_groups` | Retrieve a list of schedule groups for a team with comprehensive filtering and pagination | | **List schedules** `planly_list_schedules` | Retrieve a paginated list of schedules in a specified team | | **List team users** `planly_list_team_users` | List all users that belong to a specific team | | **List teams** `planly_list_teams` | Retrieve all teams that the authenticated user belongs to | | **Create team** `planly_create_team` | Create a new team in Planly | | **Edit team** `planly_edit_team` | Edit team details such as name in Planly | | **Import media from URL** `planly_import_media_from_url` | Import media from a URL to your team | | **Start media upload** `planly_start_media_upload` | Start the upload process for a media file | ## Example prompts **Complete Ai Prompt** > Use Planly to complete ai prompt and walk me through the result in plain English. **Get Ai Credits** > Pull the relevant data from Planly, summarize it in plain English, and point out anything that needs attention. **Get Team** > Pull the relevant data from Planly, summarize it in plain English, and point out anything that needs attention. **List Channels** > List the relevant items in Planly, 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 Planly working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Planly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Planly 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 Planly. | 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 Planly actions to the runtime in a format your agent can reliably use. | 15 tools for Planly are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Planly 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 Planly in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Planly 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 Planly 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 Planly 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 Planly tools Planly 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 Planly 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. ### Planly 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 Planly 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 Planly integration? Yes. ClawLink is the fastest way to connect Hermes to Planly: link your Planly account once in the browser and Hermes Agent can call the Planly API through 15 ready-made tools — no custom code or token handling. ### How do I connect Planly 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 Planly in the dashboard and Hermes can use it from the next message — no config files, and the Planly key you paste is stored server-side instead of in your environment. ### How long does it take to connect Planly to Hermes Agent? About two minutes. Sign in, click Connect next to Planly in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Planly 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 Planly working from chat. ### Hermes paired but still can't use Planly 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 - [ActiveCampaign](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/hermes/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Connect Mailchimp](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences