# How to connect Bettercontact to Hermes Agent (paste one key, 5 tools)

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

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

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

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

Verify the connection by asking Hermes:

> Use Bettercontact to check credits balance 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 Bettercontact is connected in the dashboard, that agent calls the same 5 Bettercontact 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).

## Bettercontact MCP for Hermes

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

## What the Hermes Agent Bettercontact integration can do

5 Bettercontact tools are ready for Hermes Agent once the account is connected.

### All 5 Bettercontact tools for Hermes

| Tool | What it does |
|---|---|
| **Check credits balance** `bettercontact_check_credits_balance` | Check the remaining credits balance for a BetterContact account |
| **Get enrichment results** `bettercontact_get_enrichment_results` | Retrieve enrichment results for a specific request ID |
| **Get lead finder results** `bettercontact_get_lead_finder_results` | Retrieve results from a submitted Lead Finder search |
| **Create lead finder search** `bettercontact_create_lead_finder_search` | Create a new Lead Finder search to discover leads based on company and people criteria |
| **Enrich leads** `bettercontact_enrich_leads` | Create a lead enrichment request for work emails and direct phone numbers |

## Example prompts

**Check Credits Balance**

> Use Bettercontact to check credits balance and walk me through the result in plain English.

**Get Enrichment Results**

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

**Get Lead Finder Results**

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

**Create Lead Finder Search**

> Search Bettercontact for what I need, summarize the results, and tell me the next best action.

## 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 Bettercontact working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

### Hermes paired but still can't use Bettercontact
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 HubSpot integration](https://claw-link.dev/hermes/hubspot) — Manage contacts, deals, and pipelines
- [CentralStationCRM](https://claw-link.dev/hermes/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships.
- [Salesforce](https://claw-link.dev/hermes/salesforce) — Manage CRM data and workflows