# How to connect JobNimbus to Hermes Agent (paste one key, 21 tools) > Connect JobNimbus to Hermes with ClawLink: paste your JobNimbus key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/jobnimbus Most guides for giving Hermes Agent JobNimbus 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 JobNimbus setup: pair once in the browser and your always-on Hermes agent can act on JobNimbus 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 JobNimbus. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect JobNimbus** — 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 jobnimbus # connect JobNimbus (browser OAuth) npx -y @useclawlink/cli actions jobnimbus # list available actions npx -y @useclawlink/cli run jobnimbus --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 JobNimbus in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your JobNimbus API key once. Verify the connection by asking Hermes: > Use JobNimbus to account get settings 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 JobNimbus is connected in the dashboard, that agent calls the same 21 JobNimbus 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). ## JobNimbus MCP for Hermes Looking for a JobNimbus MCP server for Hermes Agent? ClawLink connects JobNimbus to Hermes Agent and exposes 21 JobNimbus 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 JobNimbus integration](https://claw-link.dev/openclaw/jobnimbus) works the same way. ## What the Hermes Agent JobNimbus integration can do 21 JobNimbus tools are ready for Hermes Agent once the account is connected. ### All 21 JobNimbus tools for Hermes | Tool | What it does | |---|---| | **Account get settings** `jobnimbus_account_get_settings` | Retrieve account-wide settings (workflows, types, sources) | | **Activity get** `jobnimbus_activity_get` | Retrieves a specific JobNimbus activity by its unique jnid | | **Contact get** `jobnimbus_contact_get` | Retrieve a contact by ID | | **Contact list** `jobnimbus_contact_list` | List all contacts | | **File get** `jobnimbus_file_get` | Retrieves the raw content of a specific file attachment from JobNimbus by its unique ID | | **List activities** `jobnimbus_list_activities` | Retrieve all activities | | **List invoices** `jobnimbus_list_invoices` | List all invoices (v2) | | **List material orders** `jobnimbus_list_material_orders` | List all material orders (v2) | | **List payments** `jobnimbus_list_payments` | Retrieve payments list with optional filters | | **List products** `jobnimbus_list_products` | List all products | | **List workorders** `jobnimbus_list_workorders` | Retrieve all work orders (v2) | | **Product get** `jobnimbus_product_get` | Retrieves detailed information about a specific JobNimbus product using its jnid | | **Task list** `jobnimbus_task_list` | List all tasks | | **Utility get uoms** `jobnimbus_utility_get_uoms` | Retrieve list of supported units of measure | | **Account create location** `jobnimbus_account_create_location` | Create a new location in JobNimbus | | **Contact update** `jobnimbus_contact_update` | Update an existing contact | | **Create file type** `jobnimbus_create_file_type` | Creates a new file attachment type in JobNimbus | | **Create material order** `jobnimbus_create_material_order` | Creates a new material order in JobNimbus | | **Create task** `jobnimbus_create_task` | Create a new task | | **Create workflow status** `jobnimbus_create_workflow_status` | Create a new status in an existing workflow | | **Update task** `jobnimbus_update_task` | Update an existing JobNimbus task by its jnid | ## Example prompts **Account Get Settings** > Use JobNimbus to account get settings and walk me through the result in plain English. **Activity Get** > Use JobNimbus to activity get and walk me through the result in plain English. **Contact Get** > Use JobNimbus to contact get and walk me through the result in plain English. **Contact List** > Use JobNimbus to contact list and walk me through the result in plain English. ## 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 JobNimbus working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the JobNimbus API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected JobNimbus 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 JobNimbus. | 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 JobNimbus actions to the runtime in a format your agent can reliably use. | 21 tools for JobNimbus are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes JobNimbus 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 JobNimbus in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the JobNimbus 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 JobNimbus 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 JobNimbus 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 JobNimbus tools JobNimbus 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 JobNimbus 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. ### JobNimbus 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 JobNimbus 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 JobNimbus integration? Yes. ClawLink is the fastest way to connect Hermes to JobNimbus: link your JobNimbus account once in the browser and Hermes Agent can call the JobNimbus API through 21 ready-made tools — no custom code or token handling. ### How do I connect JobNimbus 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 JobNimbus in the dashboard and Hermes can use it from the next message — no config files, and the JobNimbus key you paste is stored server-side instead of in your environment. ### How long does it take to connect JobNimbus to Hermes Agent? About two minutes. Sign in, click Connect next to JobNimbus in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring JobNimbus 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 JobNimbus working from chat. ### Hermes paired but still can't use JobNimbus 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 HubSpot integration](https://claw-link.dev/hermes/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM tools](https://claw-link.dev/hermes/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Connect Salesforce](https://claw-link.dev/hermes/salesforce) — Manage CRM data and workflows