# How to connect Headout to Hermes Agent (paste one key, 8 tools)

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

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

Most guides for giving Hermes Agent Headout 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 Headout setup: pair once in the browser and your always-on Hermes agent can act on Headout 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 Headout.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Headout** — 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 headout  # connect Headout (browser OAuth)
npx -y @useclawlink/cli actions headout  # list available actions
npx -y @useclawlink/cli run headout <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 Headout in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Headout API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Headout, 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 Headout is connected in the dashboard, that agent calls the same 8 Headout 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).

## Headout MCP for Hermes

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

## What the Hermes Agent Headout integration can do

8 Headout tools are ready for Hermes Agent once the account is connected.

### All 8 Headout tools for Hermes

| Tool | What it does |
|---|---|
| **Get product by ID** `headout_get_product_by_id` | Retrieve detailed product information by product ID |
| **List categories v2** `headout_list_categories_v2` | Fetch all available activity categories for a specific city using V2 API |
| **List cities** `headout_list_cities` | List all active cities with pagination support |
| **List collections v2** `headout_list_collections_v2` | Fetch all collections for a specific city using V2 API with pagination support |
| **List inventory by variant** `headout_list_inventory_by_variant` | Retrieve available inventory and pricing for a specific product variant |
| **List products by category** `headout_list_products_by_category` | List product listings filtered by category ID with pagination support |
| **List products v2** `headout_list_products_v2` | Fetch products using Headout V2 API with filtering by city, collection, category, or subcategory |
| **List subcategories v2** `headout_list_subcategories_v2` | Fetch all subcategories for a specific city using V2 API |

## Example prompts

**Get Product By Id**

> Pull the relevant data from Headout, summarize it in plain English, and point out anything that needs attention.

**List Categories V2**

> List the relevant items in Headout, group them by priority, and recommend what Hermes should do next.

**List Cities**

> List the relevant items in Headout, group them by priority, and recommend what Hermes should do next.

**List Collections V2**

> List the relevant items in Headout, 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 Headout working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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

- [Cal.com](https://claw-link.dev/hermes/cal) — Schedule and manage bookings through Cal.com
- [Bookingmood tools](https://claw-link.dev/hermes/bookingmood) — Bookingmood provides flexible, commission-free booking software for rental businesses of all sizes, enabling seamless integration with your website.
- [Eventbrite tools](https://claw-link.dev/hermes/eventbrite) — Create and manage events, tickets, and attendees