# How to connect OptimoRoute to Hermes Agent (paste one key, 17 tools) > Connect OptimoRoute to Hermes with ClawLink: paste your OptimoRoute key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/optimoroute Most guides for giving Hermes Agent OptimoRoute 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 OptimoRoute setup: pair once in the browser and your always-on Hermes agent can act on OptimoRoute 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 OptimoRoute. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect OptimoRoute** — 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 optimoroute # connect OptimoRoute (browser OAuth) npx -y @useclawlink/cli actions optimoroute # list available actions npx -y @useclawlink/cli run optimoroute --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 OptimoRoute in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your OptimoRoute API key once. Verify the connection by asking Hermes: > Pull the relevant data from OptimoRoute, 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 OptimoRoute is connected in the dashboard, that agent calls the same 17 OptimoRoute 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). ## OptimoRoute MCP for Hermes Looking for a OptimoRoute MCP server for Hermes Agent? ClawLink connects OptimoRoute to Hermes Agent and exposes 17 OptimoRoute 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 OptimoRoute integration](https://claw-link.dev/openclaw/optimoroute) works the same way. ## What the Hermes Agent OptimoRoute integration can do 17 OptimoRoute tools are ready for Hermes Agent once the account is connected. The 14 below are the ones people reach for most; your agent can call all 17. ### 14 of 17 OptimoRoute tools for Hermes | Tool | What it does | |---|---| | **Get completion details** `optimoroute_get_completion_details` | Retrieve completion details for one or more orders including proof of delivery data | | **Get drivers** `optimoroute_get_drivers` | Retrieve all drivers in the system | | **Get events** `optimoroute_get_events` | Retrieve mobile events from drivers' field operations | | **Get orders** `optimoroute_get_orders` | Retrieve one or more orders from OptimoRoute | | **Get planning status** `optimoroute_get_planning_status` | Retrieve the status of an active planning/optimization process | | **Get routes** `optimoroute_get_routes` | Retrieve all planned routes for a given date | | **Get scheduling info** `optimoroute_get_scheduling_info` | Retrieve scheduling information for a specific order | | **Search orders** `optimoroute_search_orders` | Search for orders in OptimoRoute based on criteria | | **Create or update orders** `optimoroute_create_or_update_orders` | Bulk create, update, or replace multiple orders at once without geocoding | | **Create order** `optimoroute_create_order` | Create a new order or update an existing order in OptimoRoute | | **Start planning** `optimoroute_start_planning` | Start the planning/optimization process for a specified date or date range | | **Update drivers parameters** `optimoroute_update_drivers_parameters` | Update parameters of multiple drivers for specified dates in bulk (max 500 per request) | | **Stop planning** `optimoroute_stop_planning` | Stop an active planning/optimization process | | **Update driver parameters** `optimoroute_update_driver_parameters` | Update driver parameters for a specific date including work times, vehicle assignment, and | ## Example prompts **Get Completion Details** > Pull the relevant data from OptimoRoute, summarize it in plain English, and point out anything that needs attention. **Get Drivers** > Pull the relevant data from OptimoRoute, summarize it in plain English, and point out anything that needs attention. **Get Events** > Pull the relevant data from OptimoRoute, summarize it in plain English, and point out anything that needs attention. **Get Orders** > Pull the relevant data from OptimoRoute, 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 OptimoRoute working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the OptimoRoute API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected OptimoRoute 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 OptimoRoute. | 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 OptimoRoute actions to the runtime in a format your agent can reliably use. | 17 tools for OptimoRoute are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes OptimoRoute 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 OptimoRoute in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the OptimoRoute 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 OptimoRoute 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 OptimoRoute 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 OptimoRoute tools OptimoRoute 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 OptimoRoute 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. ### OptimoRoute 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 OptimoRoute 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 OptimoRoute integration? Yes. ClawLink is the fastest way to connect Hermes to OptimoRoute: link your OptimoRoute account once in the browser and Hermes Agent can call the OptimoRoute API through 17 ready-made tools — no custom code or token handling. ### How do I connect OptimoRoute 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 OptimoRoute in the dashboard and Hermes can use it from the next message — no config files, and the OptimoRoute key you paste is stored server-side instead of in your environment. ### How long does it take to connect OptimoRoute to Hermes Agent? About two minutes. Sign in, click Connect next to OptimoRoute in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring OptimoRoute 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 OptimoRoute working from chat. ### Hermes paired but still can't use OptimoRoute 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 - [Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints