# How to connect CompanyCam to Hermes Agent (paste one key, 24 tools) > Connect CompanyCam to Hermes with ClawLink: paste your CompanyCam key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/companycam Most guides for giving Hermes Agent CompanyCam 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 CompanyCam setup: pair once in the browser and your always-on Hermes agent can act on CompanyCam 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 CompanyCam. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect CompanyCam** — 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 companycam # connect CompanyCam (browser OAuth) npx -y @useclawlink/cli actions companycam # list available actions npx -y @useclawlink/cli run companycam --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 CompanyCam in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your CompanyCam API key once. Verify the connection by asking Hermes: > Pull the relevant data from CompanyCam, 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 CompanyCam is connected in the dashboard, that agent calls the same 24 CompanyCam 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). ## CompanyCam MCP for Hermes Looking for a CompanyCam MCP server for Hermes Agent? ClawLink connects CompanyCam to Hermes Agent and exposes 24 CompanyCam 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 CompanyCam integration](https://claw-link.dev/openclaw/companycam) works the same way. ## What the Hermes Agent CompanyCam integration can do 24 CompanyCam tools are ready for Hermes Agent once the account is connected. ### All 24 CompanyCam tools for Hermes | Tool | What it does | |---|---| | **Get account context** `companycam_get_account_context` | Return the connected CompanyCam user and company so an agent can identify the account, role | | **Get photo** `companycam_get_photo` | Get one CompanyCam photo by ID | | **Get project** `companycam_get_project` | Get one CompanyCam project by ID | | **List comments** `companycam_list_comments` | List comments attached to either a CompanyCam project or photo | | **List customers** `companycam_list_customers` | List or search CompanyCam customers by name or contact text | | **List labels** `companycam_list_labels` | List reusable CompanyCam project labels that can be attached to projects | | **List project photos** `companycam_list_project_photos` | List and filter photos in a CompanyCam project by tags, users, or groups, one cursor page at a | | **List project tasks** `companycam_list_project_tasks` | List tasks for a CompanyCam project, including status, completion, assignees, and attached media | | **List projects** `companycam_list_projects` | List projects with optional lifecycle and assigned-user filters, one cursor page at a time | | **List tags** `companycam_list_tags` | List reusable CompanyCam media tags and return an opaque cursor for the next page | | **List users** `companycam_list_users` | List CompanyCam users available for task assignment and project workflows | | **Search projects** `companycam_search_projects` | Search CompanyCam projects by a free-text query when project list filters are insufficient | | **Add comment** `companycam_add_comment` | Add a comment to either a CompanyCam project or photo | | **Add photo tags** `companycam_add_photo_tags` | Attach media tags by display name | | **Add project labels** `companycam_add_project_labels` | Attach project labels by display name | | **Add project photo from URL** `companycam_add_project_photo_from_url` | Add a photo to a CompanyCam project by having CompanyCam fetch a publicly reachable HTTPS image | | **Create customer** `companycam_create_customer` | Create a CompanyCam customer with optional contact details, company status, notes, address, and | | **Create project** `companycam_create_project` | Create a CompanyCam project with its required address and optional contact, customer, location | | **Create project task** `companycam_create_project_task` | Create a task on a CompanyCam project with task details and optional assignees | | **Create tag** `companycam_create_tag` | Create a reusable CompanyCam media tag for organizing photos | | **Set photo description** `companycam_set_photo_description` | Create or replace the description attached to a CompanyCam photo | | **Update customer** `companycam_update_customer` | Update the name, notes, city, or postal code of an existing CompanyCam customer | | **Update project** `companycam_update_project` | Update editable project identity, address, or primary-contact fields without changing archive | | **Update project task** `companycam_update_project_task` | Update a CompanyCam project task's details or add and retain assignees | ## Example prompts **Get Account Context** > Pull the relevant data from CompanyCam, summarize it in plain English, and point out anything that needs attention. **Get Photo** > Pull the relevant data from CompanyCam, summarize it in plain English, and point out anything that needs attention. **Get Project** > Pull the relevant data from CompanyCam, summarize it in plain English, and point out anything that needs attention. **List Comments** > List the relevant items in CompanyCam, 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 CompanyCam working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the CompanyCam API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CompanyCam 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 CompanyCam. | 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 CompanyCam actions to the runtime in a format your agent can reliably use. | 24 tools for CompanyCam are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes CompanyCam 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 CompanyCam in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the CompanyCam 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 CompanyCam 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 CompanyCam 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 CompanyCam tools CompanyCam 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 CompanyCam 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. ### CompanyCam 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 CompanyCam 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 CompanyCam integration? Yes. ClawLink is the fastest way to connect Hermes to CompanyCam: link your CompanyCam account once in the browser and Hermes Agent can call the CompanyCam API through 24 ready-made tools — no custom code or token handling. ### How do I connect CompanyCam 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 CompanyCam in the dashboard and Hermes can use it from the next message — no config files, and the CompanyCam key you paste is stored server-side instead of in your environment. ### How long does it take to connect CompanyCam to Hermes Agent? About two minutes. Sign in, click Connect next to CompanyCam in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring CompanyCam 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 CompanyCam working from chat. ### Hermes paired but still can't use CompanyCam 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 - [Trello](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards - [Connect Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [Hermes ClickUp integration](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints