# How to connect CentralStationCRM to OpenClaw (paste one key, 186 tools) > Connect CentralStationCRM to OpenClaw with ClawLink: paste your CentralStationCRM key once and 186 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/centralstationcrm The usual route to CentralStationCRM 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 CentralStationCRM setup: install one ClawHub skill, connect CentralStationCRM in the browser, and OpenClaw can call real CentralStationCRM actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/centralstationcrm ## Setup It takes three steps to connect OpenClaw to CentralStationCRM. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect CentralStationCRM** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 centralstationcrm # connect CentralStationCRM (browser OAuth) npx -y @useclawlink/cli actions centralstationcrm # list available actions npx -y @useclawlink/cli run centralstationcrm --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 CentralStationCRM in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your CentralStationCRM API key once. Verify the connection by asking OpenClaw: > Use CentralStationCRM to check connection 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 CentralStationCRM is connected in the dashboard, that agent calls the same 186 CentralStationCRM 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). ## CentralStationCRM MCP for OpenClaw Looking for a CentralStationCRM MCP server for OpenClaw? ClawLink connects CentralStationCRM to OpenClaw and exposes 186 CentralStationCRM 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 CentralStationCRM integration](https://claw-link.dev/hermes/centralstationcrm) works the same way. ## What the OpenClaw CentralStationCRM integration can do 186 CentralStationCRM 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 186. ### 30 of 186 CentralStationCRM tools for OpenClaw | Tool | What it does | |---|---| | **Check connection** `centralstationcrm_check_connection` | Verify the connection status of the CentralStationCRM API key | | **Count activities** `centralstationcrm_count_activities` | Retrieve activities count for a record, account, or user | | **Count attachments** `centralstationcrm_count_attachments` | Retrieve the total count and total file size of attachments | | **Count avatars** `centralstationcrm_count_avatars` | Retrieve the total count and total file size of avatars in the system | | **Count companies external emails** `centralstationcrm_count_companies_external_emails` | Retrieve the total amount of external emails for a specific company | | **Count deals external emails** `centralstationcrm_count_deals_external_emails` | Retrieve the total amount of external emails for a specific deal | | **Count external emails** `centralstationcrm_count_external_emails` | Retrieve the total amount of external emails | | **Count people external emails** `centralstationcrm_count_people_external_emails` | Retrieve the total amount of external emails for a specific person | | **Create attachments** `centralstationcrm_create_attachments` | Create a new attachment in CentralStationCRM | | **Create cal event** `centralstationcrm_create_cal_event` | Create a new calendar event in CentralStationCRM | | **Create cal event attendee** `centralstationcrm_create_cal_event_attendee` | Create a calendar event attendee | | **Create comment** `centralstationcrm_create_comment` | Create a new comment on an entity (task, event, protocol, etc.) | | **Count people2** `centralstationcrm_count_people2` | Retrieve the total count of people with optional filtering capabilities | | **Count projects external emails** `centralstationcrm_count_projects_external_emails` | Retrieve the total amount of external emails for a specific project | | **Count protocols** `centralstationcrm_count_protocols` | Retrieve the total number of protocols in the account | | **Get activity** `centralstationcrm_get_activity` | Retrieve details of a specific activity by its ID | | **Get API user maildrop** `centralstationcrm_get_api_user_maildrop` | Retrieve the current API user's maildrop for people and companies | | **Get attachment** `centralstationcrm_get_attachment` | Retrieve details of a specific attachment by its ID | | **Get avatars** `centralstationcrm_get_avatars` | Retrieve a specific avatar by its ID from CentralStationCRM | | **Get cal event** `centralstationcrm_get_cal_event` | Retrieve details of a specific calendar event by ID | | **Get cal event attendee** `centralstationcrm_get_cal_event_attendee` | Retrieve details of a specific calendar event attendee by ID | | **Get comment** `centralstationcrm_get_comment` | Retrieve details of a specific comment by its ID | | **Get companies avatars** `centralstationcrm_get_companies_avatars` | Retrieve a specific avatar of a company by avatar ID | | **Get companies protocols attachment** `centralstationcrm_get_companies_protocols_attachment` | Retrieve a specific attachment from a company protocol by its ID | | **Get company** `centralstationcrm_get_company` | Retrieve details of a specific company by ID from CentralStationCRM | | **Get company address** `centralstationcrm_get_company_address` | Retrieve a specific address of a company by address ID | | **Get company contact detail** `centralstationcrm_get_company_contact_detail` | Retrieve a specific contact detail by ID for a company | | **Get custom fields type** `centralstationcrm_get_custom_fields_type` | Retrieve a custom field type by its ID | | **Get deal** `centralstationcrm_get_deal` | Retrieve details of a specific deal by its ID | | **Get deals maildrop** `centralstationcrm_get_deals_maildrop` | Retrieve the maildrop email address for a specific deal | ## Example prompts **Check Connection** > Use CentralStationCRM to check connection and walk me through the result in plain English. **Count Activities** > Use CentralStationCRM to count activities and walk me through the result in plain English. **Count Attachments** > Use CentralStationCRM to count attachments and walk me through the result in plain English. **Count Avatars** > Use CentralStationCRM to count avatars and walk me through the result in plain English. ## 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 CentralStationCRM working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the CentralStationCRM API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CentralStationCRM 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 CentralStationCRM. | 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 CentralStationCRM actions to the runtime in a format your agent can reliably use. | 186 tools for CentralStationCRM are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes CentralStationCRM 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 CentralStationCRM in the browser, and the 186 tools above work from chat. There is no SDK and no config file, and the CentralStationCRM 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 CentralStationCRM skill but can't call the tools The ClawHub skill teaches OpenClaw about CentralStationCRM, but the calls run through the ClawLink plugin and your connected account. Make sure CentralStationCRM 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 CentralStationCRM 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 CentralStationCRM tools CentralStationCRM 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 CentralStationCRM 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. ### CentralStationCRM 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 CentralStationCRM has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw CentralStationCRM integration? Yes. ClawLink is the fastest way to connect OpenClaw to CentralStationCRM: link your CentralStationCRM account once in the browser and OpenClaw can call the CentralStationCRM API through 186 ready-made tools — no custom code or token handling. ### How do I add CentralStationCRM to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink CentralStationCRM skill from ClawHub, then you click Connect in the dashboard to authorize CentralStationCRM. OpenClaw calls the tools from the next message — no config files, and the CentralStationCRM key you paste is stored server-side instead of in your environment. ### How long does it take to connect CentralStationCRM to OpenClaw? About two minutes. Sign in, click Connect next to CentralStationCRM in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring CentralStationCRM 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 CentralStationCRM working from chat. ### OpenClaw installed the CentralStationCRM skill but can't call the tools The ClawHub skill teaches OpenClaw about CentralStationCRM, but the calls run through the ClawLink plugin and your connected account. Make sure CentralStationCRM 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 - [OpenClaw HubSpot integration](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows - [OpenClaw RepairShopr integration](https://claw-link.dev/openclaw/repairshopr) — RepairShopr is a comprehensive repair shop management software designed to streamline operations, manage customer relationships, and enhance business efficiency.