# How to connect Pipeline CRM to OpenClaw (paste one key, 15 tools) > Connect Pipeline CRM to OpenClaw with ClawLink: paste your Pipeline CRM key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/pipeline-crm The usual route to Pipeline 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 Pipeline CRM setup: install one ClawHub skill, connect Pipeline CRM in the browser, and OpenClaw can call real Pipeline 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 Pipeline CRM. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Pipeline 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 pipeline-crm # connect Pipeline CRM (browser OAuth) npx -y @useclawlink/cli actions pipeline-crm # list available actions npx -y @useclawlink/cli run pipeline-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 Pipeline CRM in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Pipeline CRM API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Pipeline CRM, 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 Pipeline CRM is connected in the dashboard, that agent calls the same 15 Pipeline 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). ## Pipeline CRM MCP for OpenClaw Looking for a Pipeline CRM MCP server for OpenClaw? ClawLink connects Pipeline CRM to OpenClaw and exposes 15 Pipeline 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 Pipeline CRM integration](https://claw-link.dev/hermes/pipeline-crm) works the same way. ## What the OpenClaw Pipeline CRM integration can do 15 Pipeline CRM tools are ready for OpenClaw once the account is connected. The 12 below are the ones people reach for most; your agent can call all 15. ### 12 of 15 Pipeline CRM tools for OpenClaw | Tool | What it does | |---|---| | **Get company** `pipeline_crm_get_company` | Retrieves comprehensive details for a specific company by ID from Pipeline CRM | | **Get deal** `pipeline_crm_get_deal` | Retrieve details for a specific deal by ID in Pipeline CRM | | **Get stage** `pipeline_crm_get_stage` | Retrieve details for a specific stage by ID in Pipeline CRM | | **Get task** `pipeline_crm_get_task` | Retrieve details for a specific task by ID in Pipeline CRM | | **List companies** `pipeline_crm_list_companies` | List companies in Pipeline CRM with optional filtering, sorting, and pagination | | **List leads** `pipeline_crm_list_leads` | List leads in Pipeline CRM | | **List stages** `pipeline_crm_list_stages` | List deal stages | | **List tasks** `pipeline_crm_list_tasks` | List calendar tasks | | **List users** `pipeline_crm_list_users` | List users in Pipeline CRM account with optional pagination | | **Create company** `pipeline_crm_create_company` | Creates a new company record in Pipeline CRM with contact details, address, and social media | | **Create deal** `pipeline_crm_create_deal` | Create a new deal in Pipeline CRM | | **Update company** `pipeline_crm_update_company` | Update an existing company by ID in Pipeline CRM | ## Example prompts **Get Company** > Pull the relevant data from Pipeline CRM, summarize it in plain English, and point out anything that needs attention. **Get Deal** > Pull the relevant data from Pipeline CRM, summarize it in plain English, and point out anything that needs attention. **Get Stage** > Pull the relevant data from Pipeline CRM, summarize it in plain English, and point out anything that needs attention. **Get Task** > Pull the relevant data from Pipeline 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 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 Pipeline CRM working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Pipeline CRM API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Pipeline CRM 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 Pipeline 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 Pipeline CRM actions to the runtime in a format your agent can reliably use. | 15 tools for Pipeline CRM are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Pipeline 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 Pipeline CRM in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Pipeline 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 Pipeline CRM skill but can't call the tools The ClawHub skill teaches OpenClaw about Pipeline CRM, but the calls run through the ClawLink plugin and your connected account. Make sure Pipeline 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 Pipeline 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 Pipeline CRM tools Pipeline 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 Pipeline 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. ### Pipeline 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. ### API key setup works but results look incomplete Double-check that the API key for Pipeline CRM has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Pipeline CRM integration? Yes. ClawLink is the fastest way to connect OpenClaw to Pipeline CRM: link your Pipeline CRM account once in the browser and OpenClaw can call the Pipeline CRM API through 15 ready-made tools — no custom code or token handling. ### How do I add Pipeline CRM to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Pipeline CRM skill from ClawHub, then you click Connect in the dashboard to authorize Pipeline CRM. OpenClaw calls the tools from the next message — no config files, and the Pipeline CRM key you paste is stored server-side instead of in your environment. ### How long does it take to connect Pipeline CRM to OpenClaw? About two minutes. Sign in, click Connect next to Pipeline CRM in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Pipeline CRM 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 Pipeline CRM working from chat. ### OpenClaw installed the Pipeline CRM skill but can't call the tools The ClawHub skill teaches OpenClaw about Pipeline CRM, but the calls run through the ClawLink plugin and your connected account. Make sure Pipeline 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 - [Connect HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [Connect CentralStationCRM](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce tools](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows