# How to connect Godial to OpenClaw (paste one key, 24 tools) > Connect Godial to OpenClaw 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/openclaw/godial The usual route to Godial access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Godial setup: install one ClawHub skill, connect Godial in the browser, and OpenClaw can call real Godial actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Godial. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Godial** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Godial in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Godial API key once. Verify the connection by asking OpenClaw: > List the relevant items in Godial, group them by priority, and recommend what OpenClaw should do next. ### Using a different agent? The OpenClaw 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 OpenClaw Looking for a Godial MCP server for OpenClaw? ClawLink connects Godial to OpenClaw 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 Hermes instead? The [Hermes Godial integration](https://claw-link.dev/hermes/godial) works the same way. ## What the OpenClaw Godial integration can do 24 Godial tools are ready for OpenClaw 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 OpenClaw | 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 OpenClaw should do next. **List Contacts** > List the relevant items in Godial, group them by priority, and recommend what OpenClaw should do next. **List External Lists** > List the relevant items in Godial, group them by priority, and recommend what OpenClaw should do next. **List Tasks** > List the relevant items in Godial, group them by priority, and recommend what OpenClaw 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 OpenClaw. 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 OpenClaw 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. ### OpenClaw installed the Godial skill but can't call the tools The ClawHub skill teaches OpenClaw about Godial, but the calls run through the ClawLink plugin and your connected account. Make sure Godial is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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 OpenClaw Godial integration? Yes. ClawLink is the fastest way to connect OpenClaw to Godial: link your Godial account once in the browser and OpenClaw can call the Godial API through 24 ready-made tools — no custom code or token handling. ### How do I add Godial to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Godial skill from ClawHub, then you click Connect in the dashboard to authorize Godial. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to Godial in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Godial working from chat. ### OpenClaw installed the Godial skill but can't call the tools The ClawHub skill teaches OpenClaw about Godial, but the calls run through the ClawLink plugin and your connected account. Make sure Godial is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM tools](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Connect Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows