# How to connect NetHunt CRM to OpenClaw (paste one key, 12 tools) > Connect NetHunt CRM to OpenClaw with ClawLink: paste your NetHunt CRM key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/nethunt-crm The usual route to NetHunt CRM 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 NetHunt CRM setup: install one ClawHub skill, connect NetHunt CRM in the browser, and OpenClaw can call real NetHunt CRM 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 NetHunt CRM. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect NetHunt CRM** — 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 nethunt-crm # connect NetHunt CRM (browser OAuth) npx -y @useclawlink/cli actions nethunt-crm # list available actions npx -y @useclawlink/cli run nethunt-crm --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 NetHunt CRM in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your NetHunt CRM account details once. Verify the connection by asking OpenClaw: > Use NetHunt CRM to find records and walk me through the result in plain English. ### 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 NetHunt CRM is connected in the dashboard, that agent calls the same 12 NetHunt CRM 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). ## NetHunt CRM MCP for OpenClaw Looking for a NetHunt CRM MCP server for OpenClaw? ClawLink connects NetHunt CRM to OpenClaw and exposes 12 NetHunt CRM 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 NetHunt CRM integration](https://claw-link.dev/hermes/nethunt-crm) works the same way. ## What the OpenClaw NetHunt CRM integration can do 12 NetHunt CRM tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 12. ### 11 of 12 NetHunt CRM tools for OpenClaw | Tool | What it does | |---|---| | **Find records** `nethunt_crm_find_records` | Find records by ID or text query in NetHunt CRM | | **Get new call logs** `nethunt_crm_get_new_call_logs` | Find recently created call logs in NetHunt CRM | | **Get new comments** `nethunt_crm_get_new_comments` | Find recently created record comments in a NetHunt CRM folder | | **Get new gdrive files** `nethunt_crm_get_new_gdrive_files` | Find recently created Google Drive files linked to NetHunt CRM records | | **Get new records** `nethunt_crm_get_new_records` | Find recently created records in NetHunt CRM | | **Get record changes** `nethunt_crm_get_record_changes` | Find recent record changes in a NetHunt CRM folder | | **Get updated records** `nethunt_crm_get_updated_records` | Find recently updated records in NetHunt CRM | | **List folder fields** `nethunt_crm_list_folder_fields` | List folder fields in NetHunt CRM | | **List readable folders** `nethunt_crm_list_readable_folders` | List all accessible folders in NetHunt CRM | | **List writable folders** `nethunt_crm_list_writable_folders` | List folders the user can create records in | | **Test auth** `nethunt_crm_test_auth` | Verify request credentials and test authentication | ## Example prompts **Find Records** > Use NetHunt CRM to find records and walk me through the result in plain English. **Get New Call Logs** > Pull the relevant data from NetHunt CRM, summarize it in plain English, and point out anything that needs attention. **Get New Comments** > Pull the relevant data from NetHunt CRM, summarize it in plain English, and point out anything that needs attention. **Get New Gdrive Files** > Pull the relevant data from NetHunt CRM, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential 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 NetHunt CRM working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right NetHunt CRM credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link NetHunt CRM without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for NetHunt CRM. | 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 NetHunt CRM actions to the runtime in a format your agent can reliably use. | 12 tools for NetHunt CRM are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes NetHunt CRM 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 NetHunt CRM in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the NetHunt CRM 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 NetHunt CRM skill but can't call the tools The ClawHub skill teaches OpenClaw about NetHunt CRM, but the calls run through the ClawLink plugin and your connected account. Make sure NetHunt CRM 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 NetHunt CRM 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 NetHunt CRM tools NetHunt CRM 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 NetHunt CRM 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. ### NetHunt CRM 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. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for NetHunt CRM. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a OpenClaw NetHunt CRM integration? Yes. ClawLink is the fastest way to connect OpenClaw to NetHunt CRM: link your NetHunt CRM account once in the browser and OpenClaw can call the NetHunt CRM API through 12 ready-made tools — no custom code or token handling. ### How do I add NetHunt CRM to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink NetHunt CRM skill from ClawHub, then you click Connect in the dashboard to authorize NetHunt CRM. OpenClaw calls the tools from the next message — no config files, and the NetHunt CRM key you paste is stored server-side instead of in your environment. ### How long does it take to connect NetHunt CRM to OpenClaw? About two minutes. Sign in, click Connect next to NetHunt CRM in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring NetHunt CRM up myself? The alternative to ClawLink is usually manual credential 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 NetHunt CRM working from chat. ### OpenClaw installed the NetHunt CRM skill but can't call the tools The ClawHub skill teaches OpenClaw about NetHunt CRM, but the calls run through the ClawLink plugin and your connected account. Make sure NetHunt CRM 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 - [ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences