# How to connect Crisp to OpenClaw (paste one key, 12 tools) > Connect Crisp to OpenClaw with ClawLink: paste your Crisp 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/crisp The usual route to Crisp 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 Crisp setup: install one ClawHub skill, connect Crisp in the browser, and OpenClaw can call real Crisp 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 Crisp. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Crisp** — 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 crisp # connect Crisp (browser OAuth) npx -y @useclawlink/cli actions crisp # list available actions npx -y @useclawlink/cli run crisp --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 Crisp in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Crisp API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Crisp, 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 Crisp is connected in the dashboard, that agent calls the same 12 Crisp 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). ## Crisp MCP for OpenClaw Looking for a Crisp MCP server for OpenClaw? ClawLink connects Crisp to OpenClaw and exposes 12 Crisp 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 Crisp integration](https://claw-link.dev/hermes/crisp) works the same way. ## What the OpenClaw Crisp integration can do 12 Crisp tools are ready for OpenClaw once the account is connected. ### All 12 Crisp tools for OpenClaw | Tool | What it does | |---|---| | **Get conversation** `crisp_get_conversation` | Get one conversation's status, assignment, inbox, visitor metadata, unread counts, and | | **Get people profile** `crisp_get_people_profile` | Get one customer profile by its Crisp people ID or exact email address | | **List conversation messages** `crisp_list_conversation_messages` | Return a batch of messages from a conversation, optionally before, after, or around one | | **List conversations** `crisp_list_conversations` | List or search workspace conversations with support-focused filters, one page at a time | | **List inboxes** `crisp_list_inboxes` | List configured Crisp inboxes and their operator/team membership, one page at a time | | **List operators** `crisp_list_operators` | List workspace operators and pending members with their IDs, roles, and current availability | | **List people profiles** `crisp_list_people_profiles` | List or search customer profiles by text, creation date, and sort order, one page at a time | | **Assign conversation** `crisp_assign_conversation` | Assign a conversation to one operator or explicitly remove its current operator assignment | | **Move conversation to inbox** `crisp_move_conversation_to_inbox` | Move a conversation to a specific Crisp inbox, or remove its inbox categorization when inbox_id | | **Update conversation meta** `crisp_update_conversation_meta` | Update support-relevant visitor details, subject, segments, or custom data on a conversation | | **Update conversation state** `crisp_update_conversation_state` | Set a conversation to pending, unresolved, or resolved | | **Send conversation message** `crisp_send_conversation_message` | Send a visitor-visible text reply to an existing Crisp conversation immediately; this external | ## Example prompts **Get Conversation** > Pull the relevant data from Crisp, summarize it in plain English, and point out anything that needs attention. **Get People Profile** > Pull the relevant data from Crisp, summarize it in plain English, and point out anything that needs attention. **List Conversation Messages** > List the relevant items in Crisp, group them by priority, and recommend what OpenClaw should do next. **List Conversations** > List the relevant items in Crisp, 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 Crisp working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Crisp API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Crisp 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 Crisp. | 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 Crisp actions to the runtime in a format your agent can reliably use. | 12 tools for Crisp are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Crisp 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 Crisp in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Crisp 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 Crisp skill but can't call the tools The ClawHub skill teaches OpenClaw about Crisp, but the calls run through the ClawLink plugin and your connected account. Make sure Crisp 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 Crisp 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 Crisp tools Crisp 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 Crisp 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. ### Crisp 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 Crisp has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Crisp integration? Yes. ClawLink is the fastest way to connect OpenClaw to Crisp: link your Crisp account once in the browser and OpenClaw can call the Crisp API through 12 ready-made tools — no custom code or token handling. ### How do I add Crisp to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Crisp skill from ClawHub, then you click Connect in the dashboard to authorize Crisp. OpenClaw calls the tools from the next message — no config files, and the Crisp key you paste is stored server-side instead of in your environment. ### How long does it take to connect Crisp to OpenClaw? About two minutes. Sign in, click Connect next to Crisp in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Crisp 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 Crisp working from chat. ### OpenClaw installed the Crisp skill but can't call the tools The ClawHub skill teaches OpenClaw about Crisp, but the calls run through the ClawLink plugin and your connected account. Make sure Crisp 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 SendGrid integration](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [OpenClaw Dialpad integration](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions