# How to connect Connecteam to Hermes Agent (paste one key, 16 tools) > Connect Connecteam to Hermes with ClawLink: paste your Connecteam key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/connecteam Most guides for giving Hermes Agent Connecteam 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 Connecteam setup: pair once in the browser and your always-on Hermes agent can act on Connecteam 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 Connecteam. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Connecteam** — 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 connecteam # connect Connecteam (browser OAuth) npx -y @useclawlink/cli actions connecteam # list available actions npx -y @useclawlink/cli run connecteam --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 Connecteam in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Connecteam API key once. Verify the connection by asking Hermes: > Pull the relevant data from Connecteam, 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 Connecteam is connected in the dashboard, that agent calls the same 16 Connecteam 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). ## Connecteam MCP for Hermes Looking for a Connecteam MCP server for Hermes Agent? ClawLink connects Connecteam to Hermes Agent and exposes 16 Connecteam 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 Connecteam integration](https://claw-link.dev/openclaw/connecteam) works the same way. ## What the Hermes Agent Connecteam integration can do 16 Connecteam tools are ready for Hermes Agent once the account is connected. ### All 16 Connecteam tools for Hermes | Tool | What it does | |---|---| | **Get chat** `connecteam_get_chat` | Retrieve chat conversations | | **Get custom field categories** `connecteam_get_custom_field_categories` | Retrieve all custom field categories | | **Get custom fields** `connecteam_get_custom_fields` | Retrieve all custom fields associated with the account | | **Get forms** `connecteam_get_forms` | Retrieve all form definitions from Connecteam | | **Get jobs** `connecteam_get_jobs` | Retrieve a list of job objects relevant to a specific instance ID | | **Get performance indicators** `connecteam_get_performance_indicators` | Retrieve the list of performance metric indicators | | **Get policy types** `connecteam_get_policy_types` | Retrieve available time-off policy types | | **Get publishers** `connecteam_get_publishers` | Retrieve a list of all custom publishers | | **Get schedulers** `connecteam_get_schedulers` | Retrieve a list of job schedulers associated with the account | | **Get smart groups** `connecteam_get_smart_groups` | Retrieve all smart groups associated with the account | | **Get task boards** `connecteam_get_task_boards` | Retrieve all task boards | | **Get users** `connecteam_get_users` | Retrieve a list of all users associated with your account | | **List me** `connecteam_list_me` | Retrieve account information including company name and company ID | | **Create users** `connecteam_create_users` | Create multiple users in Connecteam | | **Generate upload URL** `connecteam_generate_upload_url` | Generate a pre-signed URL for uploading a file | | **Archive users** `connecteam_archive_users` | Archive one or more users by their unique IDs | ## Example prompts **Get Chat** > Pull the relevant data from Connecteam, summarize it in plain English, and point out anything that needs attention. **Get Custom Field Categories** > Pull the relevant data from Connecteam, summarize it in plain English, and point out anything that needs attention. **Get Custom Fields** > Pull the relevant data from Connecteam, summarize it in plain English, and point out anything that needs attention. **Get Forms** > Pull the relevant data from Connecteam, 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 Connecteam working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Connecteam API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Connecteam 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 Connecteam. | 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 Connecteam actions to the runtime in a format your agent can reliably use. | 16 tools for Connecteam are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Connecteam 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 Connecteam in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Connecteam 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 Connecteam 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 Connecteam 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 Connecteam tools Connecteam 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 Connecteam 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. ### Connecteam 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 Connecteam 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 Connecteam integration? Yes. ClawLink is the fastest way to connect Hermes to Connecteam: link your Connecteam account once in the browser and Hermes Agent can call the Connecteam API through 16 ready-made tools — no custom code or token handling. ### How do I connect Connecteam 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 Connecteam in the dashboard and Hermes can use it from the next message — no config files, and the Connecteam key you paste is stored server-side instead of in your environment. ### How long does it take to connect Connecteam to Hermes Agent? About two minutes. Sign in, click Connect next to Connecteam in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Connecteam 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 Connecteam working from chat. ### Hermes paired but still can't use Connecteam 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 - [Connect Greenhouse](https://claw-link.dev/hermes/greenhouse) — Manage jobs, candidates, applications, and interviews - [Ashby tools](https://claw-link.dev/hermes/ashby) — Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process. - [Hermes Lever integration](https://claw-link.dev/hermes/lever) — Manage candidates, opportunities, interviews, and requisitions