# How to connect RepairShopr to Hermes Agent (paste one key, 147 tools)

> Connect RepairShopr to Hermes with ClawLink: paste your RepairShopr key once and 147 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/repairshopr

Most guides for giving Hermes Agent RepairShopr 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 RepairShopr setup: pair once in the browser and your always-on Hermes agent can act on RepairShopr for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

**Start here — 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.

## Setup

It takes three steps to connect Hermes to RepairShopr.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect RepairShopr** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**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 repairshopr  # connect RepairShopr (browser OAuth)
npx -y @useclawlink/cli actions repairshopr  # list available actions
npx -y @useclawlink/cli run repairshopr <action> --input '<json>'  # 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 RepairShopr in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your RepairShopr API key once.

Verify the connection by asking Hermes:

> Use RepairShopr to add estimate line item 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 RepairShopr is connected in the dashboard, that agent calls the same 147 RepairShopr 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).

## RepairShopr MCP for Hermes

Looking for a RepairShopr MCP server for Hermes Agent? ClawLink connects RepairShopr to Hermes Agent and exposes 147 RepairShopr 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 RepairShopr integration](https://claw-link.dev/openclaw/repairshopr) works the same way.

## What the Hermes Agent RepairShopr integration can do

147 RepairShopr 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 147.

### 30 of 147 RepairShopr tools for Hermes

| Tool | What it does |
|---|---|
| **Add estimate line item** `repairshopr_add_estimate_line_item` | Add a line item to an existing estimate |
| **Add purchase order line item** `repairshopr_add_purchase_order_line_item` | Add a product line item to an existing purchase order |
| **Add schedule line item** `repairshopr_add_schedule_line_item` | Add a line item to an invoice schedule |
| **Add ticket comment** `repairshopr_add_ticket_comment` | Add a comment to an existing ticket in RepairShopr |
| **Get appointment** `repairshopr_get_appointment` | Retrieve details of a specific appointment by its ID |
| **Get appointment type** `repairshopr_get_appointment_type` | Retrieve details of a specific appointment type by ID |
| **Get appointments** `repairshopr_get_appointments` | Retrieves a list of appointments from RepairShopr |
| **Get asset** `repairshopr_get_asset` | Retrieve details of a specific asset by its ID |
| **Get assets** `repairshopr_get_assets` | Retrieve a paginated list of assets |
| **Get caller ID** `repairshopr_get_caller_id` | Retrieve caller identification information based on a phone number |
| **Get canned response setting** `repairshopr_get_canned_response_setting` | Retrieve settings for Canned Responses |
| **Get contact** `repairshopr_get_contact` | Retrieve a specific contact by ID |
| **Get contacts** `repairshopr_get_contacts` | Retrieve a paginated list of contacts |
| **Get contract** `repairshopr_get_contract` | Retrieve details of a specific contract by ID |
| **Get customer** `repairshopr_get_customer` | Retrieve details of a specific customer by ID |
| **Get customer payment profiles** `repairshopr_get_customer_payment_profiles` | Retrieve a paginated list of payment profiles for a specific customer |
| **Get customers** `repairshopr_get_customers` | Retrieve a list of customers |
| **Get customers autocomplete** `repairshopr_get_customers_autocomplete` | Retrieve a list of customers for autocomplete query |
| **Get employee time clock** `repairshopr_get_employee_time_clock` | Retrieve the last time clock entry for a specific user |
| **Get estimate** `repairshopr_get_estimate` | Retrieve details of a specific estimate by ID |
| **Get estimates** `repairshopr_get_estimates` | Retrieves a paginated list of estimates from RepairShopr |
| **Get invoice** `repairshopr_get_invoice` | Retrieve details of a specific invoice by ID |
| **Get invoice ticket** `repairshopr_get_invoice_ticket` | Retrieve the associated ticket for a specific invoice |
| **Get invoices** `repairshopr_get_invoices` | Retrieve a paginated list of invoices |
| **Get latest customer** `repairshopr_get_latest_customer` | Retrieve the most recently created customer |
| **Get lead** `repairshopr_get_lead` | Retrieve details of a specific lead by its ID |
| **Get leads** `repairshopr_get_leads` | Retrieve a paginated list of leads |
| **Get me** `repairshopr_get_me` | Retrieve information about the currently authenticated user |
| **Get payment** `repairshopr_get_payment` | Retrieve details of a specific payment by ID |
| **Get payments** `repairshopr_get_payments` | Retrieve a paginated list of payments |

## Example prompts

**Add Estimate Line Item**

> Use RepairShopr to add estimate line item and walk me through the result in plain English.

**Add Purchase Order Line Item**

> Use RepairShopr to add purchase order line item and walk me through the result in plain English.

**Add Schedule Line Item**

> Use RepairShopr to add schedule line item and walk me through the result in plain English.

**Add Ticket Comment**

> Use RepairShopr to add ticket comment 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 RepairShopr working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the RepairShopr API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected RepairShopr 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 RepairShopr. | 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 RepairShopr actions to the runtime in a format your agent can reliably use. | 147 tools for RepairShopr are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes RepairShopr 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 RepairShopr in the browser, and the 147 tools above work from chat. There is no SDK and no config file, and the RepairShopr 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 RepairShopr
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 RepairShopr 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 RepairShopr tools
RepairShopr 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 RepairShopr 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.

### RepairShopr 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 RepairShopr 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 RepairShopr integration?
Yes. ClawLink is the fastest way to connect Hermes to RepairShopr: link your RepairShopr account once in the browser and Hermes Agent can call the RepairShopr API through 147 ready-made tools — no custom code or token handling.

### How do I connect RepairShopr 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 RepairShopr in the dashboard and Hermes can use it from the next message — no config files, and the RepairShopr key you paste is stored server-side instead of in your environment.

### How long does it take to connect RepairShopr to Hermes Agent?
About two minutes. Sign in, click Connect next to RepairShopr in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring RepairShopr 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 RepairShopr working from chat.

### Hermes paired but still can't use RepairShopr
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

- [HubSpot](https://claw-link.dev/hermes/hubspot) — Manage contacts, deals, and pipelines
- [Hermes CentralStationCRM integration](https://claw-link.dev/hermes/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships.
- [Salesforce tools](https://claw-link.dev/hermes/salesforce) — Manage CRM data and workflows