# How to connect Quo to OpenClaw (paste one key, 36 tools) > Connect Quo to OpenClaw with ClawLink: paste your Quo key once and 36 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/quo The usual route to Quo 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 Quo setup: install one ClawHub skill, connect Quo in the browser, and OpenClaw can call real Quo 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 Quo. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Quo** — 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 quo # connect Quo (browser OAuth) npx -y @useclawlink/cli actions quo # list available actions npx -y @useclawlink/cli run quo --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 Quo in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Quo API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Quo, 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 Quo is connected in the dashboard, that agent calls the same 36 Quo 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). ## Quo MCP for OpenClaw Looking for a Quo MCP server for OpenClaw? ClawLink connects Quo to OpenClaw and exposes 36 Quo 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 Quo integration](https://claw-link.dev/hermes/quo) works the same way. ## What the OpenClaw Quo integration can do 36 Quo 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 36. ### 30 of 36 Quo tools for OpenClaw | Tool | What it does | |---|---| | **Get call** `quo_get_call` | Get one call and its routing, participants, status, and timing details by ID | | **Get call voicemail** `quo_get_call_voicemail` | Get voicemail processing status, transcript, duration, and recording URL for a Quo call | | **Get contact** `quo_get_contact` | Get one contact with default and custom fields by Quo contact ID | | **Get message** `quo_get_message` | Get one message by Quo message ID, including its content, related IDs, participants, delivery | | **Get phone number** `quo_get_phone_number` | Get one Quo phone number and its assignments and restrictions by ID | | **Get task** `quo_get_task` | Get one task and its current links, assignee, due date, and completion state | | **Get user** `quo_get_user` | Get one workspace user by Quo user ID | | **Get webhook** `quo_get_webhook` | Get one unified Quo webhook by its numeric ID | | **Get webhook delivery** `quo_get_webhook_delivery` | Get the payload and attempt details for one Quo webhook delivery event | | **List call recordings** `quo_list_call_recordings` | List recording segments for a Quo call in chronological order | | **List calls** `quo_list_calls` | List calls between a Quo number and one external participant with optional user and | | **List contact custom fields** `quo_list_contact_custom_fields` | List the workspace's contact custom-field definitions for constructing valid contact values | | **List contacts** `quo_list_contacts` | List contacts, optionally filtered by external IDs or source, with stable-v1 phone and custom | | **List conversations** `quo_list_conversations` | List inbox conversations with optional phone-number, user, creation-time, update-time, and | | **List messages** `quo_list_messages` | List messages exchanged by a Quo phone number and one or more participants, optionally filtered | | **List phone numbers** `quo_list_phone_numbers` | List Quo phone numbers and their assigned users, calling restrictions, and messaging | | **List tasks** `quo_list_tasks` | List workspace tasks with cursor-controlled pagination | | **List users** `quo_list_users` | List workspace users and return one cursor-controlled page | | **List webhook deliveries** `quo_list_webhook_deliveries` | List one page of delivery events for a unified Quo webhook, optionally filtered by status | | **List webhooks** `quo_list_webhooks` | List unified Quo webhooks across call, message, contact, task, and integration event families | | **Create contact** `quo_create_contact` | Create a Quo contact with standard fields, optional custom fields, and external source metadata | | **Create task** `quo_create_task` | Create a task linked to exactly one phone number, conversation, or activity | | **Create webhook** `quo_create_webhook` | Create one unified webhook subscription for selected Quo events and return its signing secret | | **Set conversation status** `quo_set_conversation_status` | Set a Quo conversation to read, done, or open | | **Set task assignee** `quo_set_task_assignee` | Assign or unassign a Quo user on a task | | **Set task completion** `quo_set_task_completion` | Complete or reopen a Quo task | | **Set task conversation link** `quo_set_task_conversation_link` | Link or unlink a Quo task and conversation | | **Set task due date** `quo_set_task_due_date` | Set or remove a Quo task's due date | | **Update contact** `quo_update_contact` | Patch selected standard, custom, or source fields on an existing Quo contact | | **Update task** `quo_update_task` | Replace both the title and description of an existing Quo task | ## Example prompts **Get Call** > Pull the relevant data from Quo, summarize it in plain English, and point out anything that needs attention. **Get Call Voicemail** > Pull the relevant data from Quo, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Quo, summarize it in plain English, and point out anything that needs attention. **Get Message** > Pull the relevant data from Quo, 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 Quo working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Quo API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Quo 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 Quo. | 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 Quo actions to the runtime in a format your agent can reliably use. | 36 tools for Quo are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Quo 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 Quo in the browser, and the 36 tools above work from chat. There is no SDK and no config file, and the Quo 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 Quo skill but can't call the tools The ClawHub skill teaches OpenClaw about Quo, but the calls run through the ClawLink plugin and your connected account. Make sure Quo 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 Quo 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 Quo tools Quo 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 Quo 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. ### Quo 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 Quo has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Quo integration? Yes. ClawLink is the fastest way to connect OpenClaw to Quo: link your Quo account once in the browser and OpenClaw can call the Quo API through 36 ready-made tools — no custom code or token handling. ### How do I add Quo to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Quo skill from ClawHub, then you click Connect in the dashboard to authorize Quo. OpenClaw calls the tools from the next message — no config files, and the Quo key you paste is stored server-side instead of in your environment. ### How long does it take to connect Quo to OpenClaw? About two minutes. Sign in, click Connect next to Quo in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Quo 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 Quo working from chat. ### OpenClaw installed the Quo skill but can't call the tools The ClawHub skill teaches OpenClaw about Quo, but the calls run through the ClawLink plugin and your connected account. Make sure Quo 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 SendGrid](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [Dialpad](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [OpenClaw Discord Bot integration](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions