# How to connect Godial to Hermes Agent (paste one key, 24 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

### 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 Godial is connected in the dashboard, that agent calls the same 24 Godial 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).

## Godial MCP for Hermes

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

## What the Hermes Agent Godial integration can do

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

### 21 of 24 Godial tools for Hermes

| Tool | What it does |
|---|---|
| **List accounts** `godial_list_accounts` | Retrieve all accounts in the authenticated GoDial account |
| **List contacts** `godial_list_contacts` | Retrieve all contacts from a specific GoDial list |
| **List external lists** `godial_list_external_lists` | Retrieve all lists in the authenticated GoDial account |
| **List tasks** `godial_list_tasks` | Retrieve all tasks in the authenticated GoDial account |
| **List teams** `godial_list_teams` | Retrieve all teams in the authenticated GoDial company |
| **View contact** `godial_view_contact` | View details of a specific contact by ID |
| **View list** `godial_view_list` | View details of a specific contact list by ID |
| **View task** `godial_view_task` | View details of a specific task by ID |
| **View team** `godial_view_team` | View details of a specific team by ID |
| **Add contact** `godial_add_contact` | Add a new contact to a GoDial CRM list |
| **Add list** `godial_add_list` | Create a new contact list in GoDial |
| **Add task** `godial_add_task` | Add a new task to GoDial |
| **Add team** `godial_add_team` | Add a new team to your GoDial company |
| **Dispose contact** `godial_dispose_contact` | Insert disposition details for a contact (e.g., call outcome) |
| **Update contact** `godial_update_contact` | Update an existing contact in GoDial CRM |
| **Update list** `godial_update_list` | Update an existing contact list in GoDial |
| **Update team** `godial_update_team` | Update an existing team in GoDial |
| **Remove contact** `godial_remove_contact` | Remove a contact from GoDial by ID |
| **Remove list** `godial_remove_list` | Remove a contact list from GoDial |
| **Remove task** `godial_remove_task` | Remove a particular task from GoDial |
| **Remove team** `godial_remove_team` | Remove a team from your GoDial company |

## Example prompts

**List Accounts**

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

**List Contacts**

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

**List External Lists**

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

**List Tasks**

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

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

## ClawLink vs. Composio

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

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

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

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

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

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