# How to connect Nutshell to OpenClaw (paste one key, 78 tools) > Connect Nutshell to OpenClaw with ClawLink: paste your Nutshell key once and 78 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/nutshell The usual route to Nutshell 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 Nutshell setup: install one ClawHub skill, connect Nutshell in the browser, and OpenClaw can call real Nutshell 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 Nutshell. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Nutshell** — 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 nutshell # connect Nutshell (browser OAuth) npx -y @useclawlink/cli actions nutshell # list available actions npx -y @useclawlink/cli run nutshell --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 Nutshell in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your Nutshell account details once. Verify the connection by asking OpenClaw: > Pull the relevant data from Nutshell, summarize it in plain English, and point out anything that needs attention. ### 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 Nutshell is connected in the dashboard, that agent calls the same 78 Nutshell 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). ## Nutshell MCP for OpenClaw Looking for a Nutshell MCP server for OpenClaw? ClawLink connects Nutshell to OpenClaw and exposes 78 Nutshell 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 Nutshell integration](https://claw-link.dev/hermes/nutshell) works the same way. ## What the OpenClaw Nutshell integration can do 78 Nutshell tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 78. ### 30 of 78 Nutshell tools for OpenClaw | Tool | What it does | |---|---| | **Get account** `nutshell_get_account` | Retrieve an account from Nutshell | | **Get accounts customfields** `nutshell_get_accounts_customfields` | Retrieve custom fields for a specific account in Nutshell | | **Get activities** `nutshell_get_activities` | Retrieve a single activity by ID from Nutshell CRM | | **Get contacts** `nutshell_get_contacts` | Retrieve a specific contact by ID from Nutshell CRM | | **Get contacts customfields** `nutshell_get_contacts_customfields` | Retrieve custom fields for a specific contact in Nutshell | | **Get leads** `nutshell_get_leads` | Retrieve a specific lead by ID from Nutshell CRM | | **Get leads customfields** `nutshell_get_leads_customfields` | Retrieve custom fields for a specific lead in Nutshell CRM | | **Get notes** `nutshell_get_notes` | Retrieve a single note by ID from Nutshell CRM | | **Get productcategories** `nutshell_get_productcategories` | Retrieve a single product category by ID from Nutshell CRM | | **Get tasks** `nutshell_get_tasks` | Retrieve a single task by ID from Nutshell CRM | | **List accounts customfield attributes** `nutshell_list_accounts_customfield_attributes` | Retrieve all account custom field attributes from Nutshell CRM | | **List accounts fields** `nutshell_list_accounts_fields` | Retrieve all available fields for accounts in Nutshell | | **List accounts list items** `nutshell_list_accounts_list_items` | Retrieve list items for all accounts in Nutshell CRM | | **List accounttypes** `nutshell_list_accounttypes` | Retrieve a list of all account types from Nutshell CRM | | **List activities** `nutshell_list_activities` | Retrieve a list of activities from Nutshell CRM | | **List activitytypes** `nutshell_list_activitytypes` | Retrieve a list of all activity types from Nutshell CRM | | **List competitormaps** `nutshell_list_competitormaps` | Get a list of lead-competitor relationships from Nutshell CRM | | **List competitors** `nutshell_list_competitors` | Get a list of competitors from Nutshell CRM | | **List contacts** `nutshell_list_contacts` | Get a list of contacts from Nutshell CRM | | **List contacts customfield attributes** `nutshell_list_contacts_customfield_attributes` | Retrieve all available custom field attributes for contacts in Nutshell | | **List contacts fields** `nutshell_list_contacts_fields` | Retrieve all available fields for contacts in Nutshell | | **List contacts list items** `nutshell_list_contacts_list_items` | Retrieve list items for all contacts in Nutshell CRM | | **List deleted events** `nutshell_list_deleted_events` | Get a feed of deletion events from Nutshell CRM | | **List editions** `nutshell_list_editions` | Retrieve a list of all editions from Nutshell CRM | | **List events** `nutshell_list_events` | Get a list of events from Nutshell CRM | | **List filters** `nutshell_list_filters` | Get saved filters from Nutshell CRM | | **List forms** `nutshell_list_forms` | Get all forms from Nutshell | | **List industries** `nutshell_list_industries` | Retrieve a list of all industries from Nutshell CRM | | **List invoices** `nutshell_list_invoices` | Get a list of invoices from Nutshell CRM | | **List leads** `nutshell_list_leads` | Get a list of leads from Nutshell CRM | ## Example prompts **Get Account** > Pull the relevant data from Nutshell, summarize it in plain English, and point out anything that needs attention. **Get Accounts Customfields** > Pull the relevant data from Nutshell, summarize it in plain English, and point out anything that needs attention. **Get Activities** > Pull the relevant data from Nutshell, summarize it in plain English, and point out anything that needs attention. **Get Contacts** > Pull the relevant data from Nutshell, 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 Nutshell working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right Nutshell 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 Nutshell without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Nutshell. | 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 Nutshell actions to the runtime in a format your agent can reliably use. | 78 tools for Nutshell are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Nutshell 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 Nutshell in the browser, and the 78 tools above work from chat. There is no SDK and no config file, and the Nutshell 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 Nutshell skill but can't call the tools The ClawHub skill teaches OpenClaw about Nutshell, but the calls run through the ClawLink plugin and your connected account. Make sure Nutshell 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 Nutshell 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 Nutshell tools Nutshell 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 Nutshell 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. ### Nutshell 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 Nutshell. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a OpenClaw Nutshell integration? Yes. ClawLink is the fastest way to connect OpenClaw to Nutshell: link your Nutshell account once in the browser and OpenClaw can call the Nutshell API through 78 ready-made tools — no custom code or token handling. ### How do I add Nutshell to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Nutshell skill from ClawHub, then you click Connect in the dashboard to authorize Nutshell. OpenClaw calls the tools from the next message — no config files, and the Nutshell key you paste is stored server-side instead of in your environment. ### How long does it take to connect Nutshell to OpenClaw? About two minutes. Sign in, click Connect next to Nutshell in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Nutshell 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 Nutshell working from chat. ### OpenClaw installed the Nutshell skill but can't call the tools The ClawHub skill teaches OpenClaw about Nutshell, but the calls run through the ClawLink plugin and your connected account. Make sure Nutshell 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 - [Connect HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [OpenClaw Salesforce integration](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows