# How to connect Avoma to OpenClaw (paste one key, 16 tools) > Connect Avoma to OpenClaw with ClawLink: paste your Avoma key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/avoma The usual route to Avoma 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 Avoma setup: install one ClawHub skill, connect Avoma in the browser, and OpenClaw can call real Avoma 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 Avoma. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Avoma** — 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 avoma # connect Avoma (browser OAuth) npx -y @useclawlink/cli actions avoma # list available actions npx -y @useclawlink/cli run avoma --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 Avoma in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Avoma API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Avoma, 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 Avoma is connected in the dashboard, that agent calls the same 16 Avoma 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). ## Avoma MCP for OpenClaw Looking for a Avoma MCP server for OpenClaw? ClawLink connects Avoma to OpenClaw and exposes 16 Avoma 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 Avoma integration](https://claw-link.dev/hermes/avoma) works the same way. ## What the OpenClaw Avoma integration can do 16 Avoma tools are ready for OpenClaw once the account is connected. ### All 16 Avoma tools for OpenClaw | Tool | What it does | |---|---| | **Get call** `avoma_get_call` | Retrieve one externally ingested Avoma call by the dialer system's external ID | | **Get engagement summary** `avoma_get_engagement_summary` | Aggregate Avoma engagement metrics across visible users for a required UTC date range and | | **Get meeting** `avoma_get_meeting` | Retrieve one meeting by UUID, including processing/readiness state and optionally CRM | | **Get meeting analysis** `avoma_get_meeting_analysis` | Return Avoma's AI insights, topical and speaker segments, and sentiment records for one | | **Get recording** `avoma_get_recording` | Get time-limited audio and video URLs for a meeting recording | | **List calls** `avoma_list_calls` | List externally ingested calls in a required UTC date range, optionally filtered by inbound or | | **List configuration resources** `avoma_list_configuration_resources` | List one Avoma configuration catalog: custom categories, smart categories, scorecards | | **List engagement metrics** `avoma_list_engagement_metrics` | List per-user Avoma engagement metrics over a required UTC date range with meeting and user | | **List meetings** `avoma_list_meetings` | Find meetings visible to the connected Avoma user within a required UTC date range, with | | **List notes** `avoma_list_notes` | Retrieve Avoma notes for meetings in a required UTC date range, optionally narrowed to a | | **List scorecard evaluations** `avoma_list_scorecard_evaluations` | List Avoma scorecard evaluations, optionally filtered by UTC date range, scorecard templates | | **List snippets** `avoma_list_snippets` | Find user-created or AI-generated meeting snippets by meeting UUID or by a UTC date range of at | | **List transcriptions** `avoma_list_transcriptions` | Find full meeting transcriptions by meeting UUID or by a UTC date range, with attendee and CRM | | **List users** `avoma_list_users` | Return users visible in the Avoma organization, including their UUID, email, role, teams, and | | **List webhooks** `avoma_list_webhooks` | Audit the connected organization's active Avoma webhook subscriptions without reading signing | | **Create call** `avoma_create_call` | Submit an externally hosted call recording to Avoma for asynchronous processing | ## Example prompts **Get Call** > Pull the relevant data from Avoma, summarize it in plain English, and point out anything that needs attention. **Get Engagement Summary** > Pull the relevant data from Avoma, summarize it in plain English, and point out anything that needs attention. **Get Meeting** > Pull the relevant data from Avoma, summarize it in plain English, and point out anything that needs attention. **Get Meeting Analysis** > Pull the relevant data from Avoma, 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 Avoma working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Avoma API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Avoma 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 Avoma. | 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 Avoma actions to the runtime in a format your agent can reliably use. | 16 tools for Avoma are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Avoma 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 Avoma in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Avoma 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 Avoma skill but can't call the tools The ClawHub skill teaches OpenClaw about Avoma, but the calls run through the ClawLink plugin and your connected account. Make sure Avoma 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 Avoma 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 Avoma tools Avoma 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 Avoma 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. ### Avoma 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 Avoma has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Avoma integration? Yes. ClawLink is the fastest way to connect OpenClaw to Avoma: link your Avoma account once in the browser and OpenClaw can call the Avoma API through 16 ready-made tools — no custom code or token handling. ### How do I add Avoma to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Avoma skill from ClawHub, then you click Connect in the dashboard to authorize Avoma. OpenClaw calls the tools from the next message — no config files, and the Avoma key you paste is stored server-side instead of in your environment. ### How long does it take to connect Avoma to OpenClaw? About two minutes. Sign in, click Connect next to Avoma in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Avoma 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 Avoma working from chat. ### OpenClaw installed the Avoma skill but can't call the tools The ClawHub skill teaches OpenClaw about Avoma, but the calls run through the ClawLink plugin and your connected account. Make sure Avoma 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 - [DataRobot tools](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [OpenClaw Chatbotkit integration](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API tools](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.