# How to connect Fleetio to Hermes Agent (paste one key, 34 tools) > Connect Fleetio to Hermes with ClawLink: paste your Fleetio key once and 34 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/fleetio Most guides for giving Hermes Agent Fleetio 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 Fleetio setup: pair once in the browser and your always-on Hermes agent can act on Fleetio 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 Fleetio. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Fleetio** — 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 fleetio # connect Fleetio (browser OAuth) npx -y @useclawlink/cli actions fleetio # list available actions npx -y @useclawlink/cli run fleetio --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 Fleetio in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fleetio API key once. Verify the connection by asking Hermes: > Pull the relevant data from Fleetio, 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 Fleetio is connected in the dashboard, that agent calls the same 34 Fleetio 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). ## Fleetio MCP for Hermes Looking for a Fleetio MCP server for Hermes Agent? ClawLink connects Fleetio to Hermes Agent and exposes 34 Fleetio 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 Fleetio integration](https://claw-link.dev/openclaw/fleetio) works the same way. ## What the Hermes Agent Fleetio integration can do 34 Fleetio tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 34. ### 30 of 34 Fleetio tools for Hermes | Tool | What it does | |---|---| | **Get contact** `fleetio_get_contact` | Retrieve one Fleetio contact by ID for assignment, issue, or maintenance workflows | | **Get issue** `fleetio_get_issue` | Retrieve full details for one Fleetio issue by ID | | **Get service entry** `fleetio_get_service_entry` | Retrieve one Fleetio service entry by ID, including its status, maintenance tasks, issues | | **Get vehicle** `fleetio_get_vehicle` | Retrieve full current details for one Fleetio vehicle by ID | | **Get work order** `fleetio_get_work_order` | Retrieve full details for one Fleetio work order by ID | | **List accounts** `fleetio_list_accounts` | Return Fleetio account identity, plan, state, and permission or feature context for the | | **List contacts** `fleetio_list_contacts` | Find Fleetio contacts using bounded cursor pagination and common identity or employment filters | | **List fuel entries** `fleetio_list_fuel_entries` | Find Fleetio fuel entries by vehicle, vendor, external ID, or date range using bounded cursor | | **List issues** `fleetio_list_issues` | Find Fleetio issues by vehicle, state, issue number, assigned contact, due date, or reported | | **List meter entries** `fleetio_list_meter_entries` | Find Fleetio primary or secondary meter readings by vehicle, meterable asset, category, or date | | **List reference data** `fleetio_list_reference_data` | List one Fleetio reference collection used by vehicle, issue, work-order, service, fuel | | **List service entries** `fleetio_list_service_entries` | List Fleetio service entries by reference, status, or completion-date range, with sorting and | | **List service reminders** `fleetio_list_service_reminders` | Find due, overdue, snoozed, or upcoming Fleetio service reminders by vehicle or service task | | **List vehicles** `fleetio_list_vehicles` | Find active Fleetio vehicles by name, VIN, license plate, group, status, or type, with cursor | | **List work orders** `fleetio_list_work_orders` | Find Fleetio work orders by vehicle, vendor, contact, number, status, or purchase order | | **Archive contact** `fleetio_archive_contact` | Archive one Fleetio contact by ID | | **Archive vehicle** `fleetio_archive_vehicle` | Archive one Fleetio vehicle by ID | | **Change issue state** `fleetio_change_issue_state` | Close, resolve, or reopen one Fleetio issue using the dedicated lifecycle endpoint for that | | **Create contact** `fleetio_create_contact` | Create a Fleetio contact with a required first name and optional common business identity fields | | **Create fuel entry** `fleetio_create_fuel_entry` | Create a Fleetio fuel entry and its required meter reading for a vehicle | | **Create issue** `fleetio_create_issue` | Report a Fleetio issue for a vehicle or equipment asset with required timing and summary plus | | **Create meter entry** `fleetio_create_meter_entry` | Record a primary or secondary Fleetio meter reading for a vehicle | | **Create vehicle** `fleetio_create_vehicle` | Create a Fleetio vehicle with its required name, primary meter unit, status, and type, plus | | **Restore contact** `fleetio_restore_contact` | Restore one archived Fleetio contact by ID | | **Restore vehicle** `fleetio_restore_vehicle` | Restore one archived Fleetio vehicle by ID | | **Update contact** `fleetio_update_contact` | Update selected business identity, communication, employment, or group fields on one Fleetio | | **Update fuel entry** `fleetio_update_fuel_entry` | Correct selected timestamp, volume, meter, vendor, fuel type, price, flag, or reference fields | | **Update issue** `fleetio_update_issue` | Update issue content, priority, due date, or assignments without changing the issue lifecycle | | **Update meter entry** `fleetio_update_meter_entry` | Correct the timestamp, value, or void state of one Fleetio meter entry, or change its meter | | **Update vehicle** `fleetio_update_vehicle` | Update selected identity, classification, or assignment fields on one Fleetio vehicle; omitted | ## Example prompts **Get Contact** > Pull the relevant data from Fleetio, summarize it in plain English, and point out anything that needs attention. **Get Issue** > Pull the relevant data from Fleetio, summarize it in plain English, and point out anything that needs attention. **Get Service Entry** > Pull the relevant data from Fleetio, summarize it in plain English, and point out anything that needs attention. **Get Vehicle** > Pull the relevant data from Fleetio, 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 Fleetio working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Fleetio API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fleetio 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 Fleetio. | 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 Fleetio actions to the runtime in a format your agent can reliably use. | 34 tools for Fleetio are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Fleetio 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 Fleetio in the browser, and the 34 tools above work from chat. There is no SDK and no config file, and the Fleetio 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 Fleetio 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 Fleetio 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 Fleetio tools Fleetio 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 Fleetio 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. ### Fleetio 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 Fleetio 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 Fleetio integration? Yes. ClawLink is the fastest way to connect Hermes to Fleetio: link your Fleetio account once in the browser and Hermes Agent can call the Fleetio API through 34 ready-made tools — no custom code or token handling. ### How do I connect Fleetio 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 Fleetio in the dashboard and Hermes can use it from the next message — no config files, and the Fleetio key you paste is stored server-side instead of in your environment. ### How long does it take to connect Fleetio to Hermes Agent? About two minutes. Sign in, click Connect next to Fleetio in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Fleetio 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 Fleetio working from chat. ### Hermes paired but still can't use Fleetio 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 Trello](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards - [Hermes Moco integration](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