# How to connect DocsBot AI to OpenClaw (paste one key, 38 tools) > Connect DocsBot AI to OpenClaw with ClawLink: paste your DocsBot AI key once and 38 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/docsbot-ai The usual route to DocsBot AI 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 DocsBot AI setup: install one ClawHub skill, connect DocsBot AI in the browser, and OpenClaw can call real DocsBot AI 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 DocsBot AI. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect DocsBot AI** — 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 docsbot-ai # connect DocsBot AI (browser OAuth) npx -y @useclawlink/cli actions docsbot-ai # list available actions npx -y @useclawlink/cli run docsbot-ai --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 DocsBot AI in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your DocsBot AI API key once. Verify the connection by asking OpenClaw: > Use DocsBot AI to docsbot conversation ticket creation 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 DocsBot AI is connected in the dashboard, that agent calls the same 38 DocsBot AI 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). ## DocsBot AI MCP for OpenClaw Looking for a DocsBot AI MCP server for OpenClaw? ClawLink connects DocsBot AI to OpenClaw and exposes 38 DocsBot AI 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 DocsBot AI integration](https://claw-link.dev/hermes/docsbot-ai) works the same way. ## What the OpenClaw DocsBot AI integration can do 38 DocsBot AI 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 38. ### 30 of 38 DocsBot AI tools for OpenClaw | Tool | What it does | |---|---| | **Docsbot conversation ticket creation** `docsbot_ai_docsbot_conversation_ticket_creation` | Generates a structured support ticket from a Chat Agent conversation | | **Get bot** `docsbot_ai_get_bot` | Fetch details of a specific bot by ID within a team | | **Get bot reports** `docsbot_ai_get_bot_reports` | Retrieve monthly statistical reports for a bot | | **Get bot stats** `docsbot_ai_get_bot_stats` | Retrieve comprehensive statistics and analytics for a bot over a time period or date range | | **Get source** `docsbot_ai_get_source` | Retrieve detailed information about a specific source by its ID | | **Get team** `docsbot_ai_get_team` | Fetch details of a specific team by its ID | | **Get upload URL** `docsbot_ai_get_upload_url` | Get a presigned upload URL for uploading files as sources | | **Get webhook** `docsbot_ai_get_webhook` | Retrieve details of a specific webhook by ID | | **List bots** `docsbot_ai_list_bots` | List all bots for a given team | | **List conversations** `docsbot_ai_list_conversations` | List conversation history for a bot with pagination | | **List leads** `docsbot_ai_list_leads` | List captured leads for a bot with pagination and date filtering | | **List questions** `docsbot_ai_list_questions` | List all questions asked of a specific bot | | **List research jobs** `docsbot_ai_list_research_jobs` | List all deep research jobs for a bot with pagination support | | **List sources** `docsbot_ai_list_sources` | Retrieves a paginated list of all sources for a specific bot within a team | | **List team members** `docsbot_ai_list_team_members` | List all members of a team including their roles | | **List teams** `docsbot_ai_list_teams` | List all teams | | **List webhooks** `docsbot_ai_list_webhooks` | List all registered webhooks for a bot | | **Search semantic** `docsbot_ai_search_semantic` | Perform semantic search on a bot's indexed content | | **Capture conversation lead** `docsbot_ai_capture_conversation_lead` | Capture lead information by updating conversation metadata and saving the lead | | **Create bot** `docsbot_ai_create_bot` | Create a new bot within a team | | **Create source** `docsbot_ai_create_source` | Create a new source for a bot | | **Create webhook** `docsbot_ai_create_webhook` | Create a new webhook subscription for a bot | | **Rate answer** `docsbot_ai_rate_answer` | Rate an answer from chat APIs as positive (1), neutral (0), or negative (-1) | | **Refresh source** `docsbot_ai_refresh_source` | Refresh a source to re-index its content | | **Test escalated webhook** `docsbot_ai_test_escalated_webhook` | Trigger a test delivery of the conversation.escalated webhook | | **Test lead webhook** `docsbot_ai_test_lead_webhook` | Trigger a test lead webhook delivery | | **Test research webhook** `docsbot_ai_test_research_webhook` | Trigger a deep research webhook delivery test | | **Trigger rated webhook test** `docsbot_ai_trigger_rated_webhook_test` | Trigger a conversation.rated webhook delivery test for a specific bot | | **Update bot** `docsbot_ai_update_bot` | Update a bot's configuration settings such as name, description, model, temperature, and | | **Update team** `docsbot_ai_update_team` | Update specific fields for a team | ## Example prompts **Docsbot Conversation Ticket Creation** > Use DocsBot AI to docsbot conversation ticket creation and walk me through the result in plain English. **Get Bot** > Pull the relevant data from DocsBot AI, summarize it in plain English, and point out anything that needs attention. **Get Bot Reports** > Pull the relevant data from DocsBot AI, summarize it in plain English, and point out anything that needs attention. **Get Bot Stats** > Pull the relevant data from DocsBot AI, 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 DocsBot AI working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the DocsBot AI API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected DocsBot AI 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 DocsBot AI. | 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 DocsBot AI actions to the runtime in a format your agent can reliably use. | 38 tools for DocsBot AI are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes DocsBot AI 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 DocsBot AI in the browser, and the 38 tools above work from chat. There is no SDK and no config file, and the DocsBot AI 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 DocsBot AI skill but can't call the tools The ClawHub skill teaches OpenClaw about DocsBot AI, but the calls run through the ClawLink plugin and your connected account. Make sure DocsBot AI 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 DocsBot AI 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 DocsBot AI tools DocsBot AI 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 DocsBot AI 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. ### DocsBot AI 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 DocsBot AI has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw DocsBot AI integration? Yes. ClawLink is the fastest way to connect OpenClaw to DocsBot AI: link your DocsBot AI account once in the browser and OpenClaw can call the DocsBot AI API through 38 ready-made tools — no custom code or token handling. ### How do I add DocsBot AI to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink DocsBot AI skill from ClawHub, then you click Connect in the dashboard to authorize DocsBot AI. OpenClaw calls the tools from the next message — no config files, and the DocsBot AI key you paste is stored server-side instead of in your environment. ### How long does it take to connect DocsBot AI to OpenClaw? About two minutes. Sign in, click Connect next to DocsBot AI in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring DocsBot AI 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 DocsBot AI working from chat. ### OpenClaw installed the DocsBot AI skill but can't call the tools The ClawHub skill teaches OpenClaw about DocsBot AI, but the calls run through the ClawLink plugin and your connected account. Make sure DocsBot AI 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 DataRobot integration](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. - [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 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.