# How to connect Expofp to Hermes Agent (paste one key, 18 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

## Expofp MCP for Hermes

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

## What the Hermes Agent Expofp integration can do

18 Expofp tools are ready for Hermes Agent once the account is connected. The 15 below are the ones people reach for most; your agent can call all 18.

### 15 of 18 Expofp tools for Hermes

| Tool | What it does |
|---|---|
| **Get bulk read exhibitors template** `expofp_get_bulk_read_exhibitors_template` | Get the template structure for bulk reading exhibitors from an expo |
| **Get offline archive** `expofp_get_offline_archive` | Lightweight retrieval of offline archive state that never starts a build |
| **Get session tracks** `expofp_get_session_tracks` | Retrieve all session tracks for a specific expo event |
| **List all expo extras** `expofp_list_all_expo_extras` | Retrieves all extras (additional services/items) available for a specific expo event, including |
| **List all expos** `expofp_list_all_expos` | Retrieve all expos (events/exhibitions) accessible with the authenticated ExpoFP account |
| **List categories** `expofp_list_categories` | Retrieve all categories for a specific expo event |
| **List exhibitors** `expofp_list_exhibitors` | Bulk read exhibitors from an expo with customizable response template |
| **Add category** `expofp_add_category` | Add a new category to an expo |
| **Get or create offline archive** `expofp_get_or_create_offline_archive` | Retrieve the offline archive state for a specific expo version |
| **Set exhibitor logo** `expofp_set_exhibitor_logo` | Set or remove an exhibitor logo using multipart/form-data |
| **Update category** `expofp_update_category` | Update an existing category |
| **Update exhibitor** `expofp_update_exhibitor` | Update an existing exhibitor |
| **Upsert session tracks** `expofp_upsert_session_tracks` | Create or update session tracks in bulk for an expo |
| **Upsert sessions** `expofp_upsert_sessions` | Create or update sessions in bulk for an expo event |
| **Remove category** `expofp_remove_category` | Remove a category from an expo |

## Example prompts

**Get Bulk Read Exhibitors Template**

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

**Get Offline Archive**

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

**Get Session Tracks**

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

**List All Expo Extras**

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

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

## ClawLink vs. Composio

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

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

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

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

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

### Hermes paired but still can't use Expofp
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 Cal.com integration](https://claw-link.dev/hermes/cal) — Schedule and manage bookings through Cal.com
- [Hermes Bookingmood integration](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.
- [Connect Eventbrite](https://claw-link.dev/hermes/eventbrite) — Create and manage events, tickets, and attendees
