ClawLink

How to connect Quo to OpenClaw

Connect Quo to OpenClaw with ClawLink: paste your Quo key once and 102 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Quo
Quo
QuoAPI KEYMCP

Quo, formerly OpenPhone, is a business phone platform for managing calls, messages, contacts, conversations, tasks, users, and webhooks.. Once connected, OpenClaw can read and act on Quo from chat — pairing, token refresh, and tool wiring handled for you.

102 tools

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. 1

    Install the plugin

    Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:

    openclaw plugins install clawhub:clawlink-plugin
  2. 2

    Connect Quo

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Quo?"

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:

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 — 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:

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 102 Quo tools over MCP. Full setup for MCP clients and shell agents: 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 102 Quo tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Quo integration works the same way.

What the OpenClaw Quo integration can do

102 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 102.

30 of 102 Quo tools for OpenClaw

ToolWhat it does
Get a2p registration quo_get_a2p_registrationGet the organization's A2P (10DLC) registration
Get call quo_get_callGet one call and its routing, participants, status, and timing details by ID
Get call summary quo_get_call_summaryGet the summary, suggested next steps, and processing status of a Quo call, including
Get call transcript quo_get_call_transcriptGet a detailed transcript and processing status for a Quo call, including speaker identifiers
Get call voicemail quo_get_call_voicemailGet voicemail processing status, transcript, duration, and recording URL for a Quo call
Get contact quo_get_contactGet one contact with default and custom fields by Quo contact ID
Get contact note quo_get_contact_noteRetrieve a single contact note by contact_id and note_id, including its text, attachments
Get contact property quo_get_contact_propertyRetrieve a single contact property by contact_id and property_id, including its type, label
Get legacy webhook quo_get_legacy_webhookGet a legacy v1 Quo webhook by its WH-prefixed ID, including its status, destination URL, key
Get message quo_get_messageGet one message by Quo message ID, including its content, related IDs, participants, delivery
Get organization quo_get_organizationRetrieve the Quo workspace organization associated with the connected API key, including its
Get phone number quo_get_phone_numberGet one Quo phone number and its assignments and restrictions by ID
Get phone number settings quo_get_phone_number_settingsRetrieve automatic call recording and inbound/outbound recording disclosure settings for a Quo
Get task quo_get_taskGet one task and its current links, assignee, due date, and completion state
Get user quo_get_userGet one workspace user by Quo user ID
Get webhook quo_get_webhookGet one unified Quo webhook by its numeric ID
Get webhook delivery quo_get_webhook_deliveryGet the payload and attempt details for one Quo webhook delivery event
Get workspace call quo_get_workspace_callGet one workspace call by ID, optionally including its summary and voicemail
Get workspace contact quo_get_workspace_contactRetrieve one contact in your Quo workspace by its unique contact ID
Get workspace message quo_get_workspace_messageGet one workspace message by its ID, including attached media, delivery status, participants
Get workspace phone number quo_get_workspace_phone_numberRetrieve a phone number in your Quo workspace by its ID, optionally including calling/messaging
Get workspace task quo_get_workspace_taskUsing API 2026-03-30, get one task by ID, including links, assignment, due date, status, and
Get workspace user quo_get_workspace_userUsing API 2026-03-30, retrieve one user in your Quo workspace by user ID
List call recordings quo_list_call_recordingsList recording segments for a Quo call in chronological order
List call transcripts quo_list_call_transcriptsList one page of a Quo call's transcripts using API version 2026-03-30
List calls quo_list_callsList calls between a Quo number and one external participant with optional user and
List contact custom fields quo_list_contact_custom_fieldsList the workspace's contact custom-field definitions for constructing valid contact values
List contact notes quo_list_contact_notesList one page of a contact's notes, including text, attachments, timestamps and author IDs
List contact properties quo_list_contact_propertiesList one page of a contact's properties, optionally filtered by type, including labels, values
List contact shares quo_list_contact_sharesList one page of shares for a workspace contact using GET /contacts/{contactId}/shares with Quo

Try it: find the Quo tool you need

Browse the 30 Quo tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Quo, summarize it in plain English, and point out anything that needs attention.

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.

ManualClawLink
Credential handlingCollect, 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 maintenanceYou 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 usabilityYou still need to expose the right Quo actions to the runtime in a format your agent can reliably use.102 tools for Quo are already exposed through ClawLink, so the agent can read and act from chat immediately.

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 102 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 comparison.

Troubleshooting

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.

FAQ

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 102 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.

On this page