# How to connect Kadoa to OpenClaw (paste one key, 77 tools) > Connect Kadoa to OpenClaw with ClawLink: paste your Kadoa key once and 77 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/kadoa The usual route to Kadoa 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 Kadoa setup: install one ClawHub skill, connect Kadoa in the browser, and OpenClaw can call real Kadoa 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 Kadoa. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Kadoa** — 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 kadoa # connect Kadoa (browser OAuth) npx -y @useclawlink/cli actions kadoa # list available actions npx -y @useclawlink/cli run kadoa --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 Kadoa in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Kadoa API key once. Verify the connection by asking OpenClaw: > Use Kadoa to export activity and walk me through the result in plain English. ### 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 Kadoa is connected in the dashboard, that agent calls the same 77 Kadoa 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). ## Kadoa MCP for OpenClaw Looking for a Kadoa MCP server for OpenClaw? ClawLink connects Kadoa to OpenClaw and exposes 77 Kadoa 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 Kadoa integration](https://claw-link.dev/hermes/kadoa) works the same way. ## What the OpenClaw Kadoa integration can do 77 Kadoa 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 77. ### 30 of 77 Kadoa tools for OpenClaw | Tool | What it does | |---|---| | **Export activity** `kadoa_export_activity` | Export activity events from audit logs to CSV format for compliance and audit purposes | | **Export activity workflows** `kadoa_export_activity_workflows` | Export workflow configurations and metadata as CSV for portfolio reviews and compliance | | **Fetch workflow configuration** `kadoa_fetch_workflow_configuration` | Retrieve detailed configuration of a workflow by its ID | | **Get all locations** `kadoa_get_all_locations` | Retrieves all available scraping proxy locations (countries) supported by Kadoa | | **Get crawl bucket data** `kadoa_get_crawl_bucket_data` | Retrieve file content from the Kadoa crawling bucket (HTML or screenshot) | | **Get crawl config** `kadoa_get_crawl_config` | Retrieve a crawling configuration by its ID | | **Get crawl status** `kadoa_get_crawl_status` | Fetch current status of a crawling session | | **Get crawled page content** `kadoa_get_crawled_page_content` | Retrieve content of a crawled page | | **Get crawled pages** `kadoa_get_crawled_pages` | List pages crawled during a session | | **Get event type** `kadoa_get_event_type` | Retrieve details for a specific notification event type | | **Get event types** `kadoa_get_event_types` | Retrieve supported notification event types | | **Get latest workflow data** `kadoa_get_latest_workflow_data` | Retrieves the extracted data from a Kadoa workflow's most recent run (or a specific run if | | **Get latest workflow validation** `kadoa_get_latest_workflow_validation` | Retrieves the latest validation results for the most recent job of a workflow | | **Get notification channel** `kadoa_get_notification_channel` | Retrieve details of a specific notification channel | | **Get notification logs** `kadoa_get_notification_logs` | Retrieve notification event logs with optional filtering by workflow, event type, and date range | | **Get notification setting** `kadoa_get_notification_setting` | Retrieves a specific notification setting by its unique identifier | | **Get schema** `kadoa_get_schema` | Retrieve a specific schema by its unique identifier | | **Get validation anomalies** `kadoa_get_validation_anomalies` | Retrieve all anomalies for a specific validation | | **Get validation anomalies by rule** `kadoa_get_validation_anomalies_by_rule` | Retrieve anomalies for a specific validation rule | | **Get validation config** `kadoa_get_validation_config` | Retrieve the data validation configuration for a specific workflow | | **Get validation rule** `kadoa_get_validation_rule` | Retrieve a specific validation rule by its ID | | **Get workflow audit log** `kadoa_get_workflow_audit_log` | Retrieve audit log entries for a workflow | | **Get workflow job** `kadoa_get_workflow_job` | Retrieve the current status and telemetry information for a specific workflow job | | **Get workflow run history** `kadoa_get_workflow_run_history` | Fetch workflow run history | | **Get workflow trigger** `kadoa_get_workflow_trigger` | Retrieve a specific trigger for a workflow | | **Get workflow validation results** `kadoa_get_workflow_validation_results` | Retrieves the latest validation results for a specific workflow job | | **Get workflows** `kadoa_get_workflows` | Retrieve a paginated list of workflows with optional filtering | | **Get workspace details** `kadoa_get_workspace_details` | Retrieve detailed information about a workspace (user, team, or organization) | | **List activity** `kadoa_list_activity` | Retrieve activity events from audit logs with basic filtering and pagination | | **List changes** `kadoa_list_changes` | Retrieve all data changes detected across workflows in your Kadoa account | ## Example prompts **Export Activity** > Use Kadoa to export activity and walk me through the result in plain English. **Export Activity Workflows** > Use Kadoa to export activity workflows and walk me through the result in plain English. **Fetch Workflow Configuration** > Pull the relevant data from Kadoa, summarize it in plain English, and point out anything that needs attention. **Get All Locations** > Pull the relevant data from Kadoa, 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 Kadoa working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Kadoa API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Kadoa 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 Kadoa. | 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 Kadoa actions to the runtime in a format your agent can reliably use. | 77 tools for Kadoa are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Kadoa 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 Kadoa in the browser, and the 77 tools above work from chat. There is no SDK and no config file, and the Kadoa 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 Kadoa skill but can't call the tools The ClawHub skill teaches OpenClaw about Kadoa, but the calls run through the ClawLink plugin and your connected account. Make sure Kadoa 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 Kadoa 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 Kadoa tools Kadoa 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 Kadoa 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. ### Kadoa 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 Kadoa has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Kadoa integration? Yes. ClawLink is the fastest way to connect OpenClaw to Kadoa: link your Kadoa account once in the browser and OpenClaw can call the Kadoa API through 77 ready-made tools — no custom code or token handling. ### How do I add Kadoa to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Kadoa skill from ClawHub, then you click Connect in the dashboard to authorize Kadoa. OpenClaw calls the tools from the next message — no config files, and the Kadoa key you paste is stored server-side instead of in your environment. ### How long does it take to connect Kadoa to OpenClaw? About two minutes. Sign in, click Connect next to Kadoa in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Kadoa 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 Kadoa working from chat. ### OpenClaw installed the Kadoa skill but can't call the tools The ClawHub skill teaches OpenClaw about Kadoa, but the calls run through the ClawLink plugin and your connected account. Make sure Kadoa 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 DataRobot](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. - [Connect Chatbotkit](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](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.