# How to connect DocuPipe to OpenClaw (paste one key, 13 tools) > Connect DocuPipe to OpenClaw with ClawLink: paste your DocuPipe key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/docupipe The usual route to DocuPipe 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 DocuPipe setup: install one ClawHub skill, connect DocuPipe in the browser, and OpenClaw can call real DocuPipe 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 DocuPipe. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect DocuPipe** — 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 docupipe # connect DocuPipe (browser OAuth) npx -y @useclawlink/cli actions docupipe # list available actions npx -y @useclawlink/cli run docupipe --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 DocuPipe in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your DocuPipe API key once. Verify the connection by asking OpenClaw: > Use DocuPipe to find documents 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 DocuPipe is connected in the dashboard, that agent calls the same 13 DocuPipe 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). ## DocuPipe MCP for OpenClaw Looking for a DocuPipe MCP server for OpenClaw? ClawLink connects DocuPipe to OpenClaw and exposes 13 DocuPipe 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 DocuPipe integration](https://claw-link.dev/hermes/docupipe) works the same way. ## What the OpenClaw DocuPipe integration can do 13 DocuPipe tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 13. ### 11 of 13 DocuPipe tools for OpenClaw | Tool | What it does | |---|---| | **Find documents** `docupipe_find_documents` | Browse documents by dataset and creation time, or search filenames and document IDs when query | | **Find jobs** `docupipe_find_jobs` | Retrieve one asynchronous job by ID, or list and filter jobs when job_id is omitted | | **Get account usage** `docupipe_get_account_usage` | Return current plan and credit state together with job counts and credits consumed by job type | | **Get document** `docupipe_get_document` | Retrieve a processed document, including processing state, parsed content, page count | | **Get schema** `docupipe_get_schema` | Retrieve one extraction schema and its full JSON Schema definition by ID | | **Get standardization** `docupipe_get_standardization` | Retrieve one completed standardization as structured JSON, including extraction data and field | | **List schemas** `docupipe_list_schemas` | List extraction schemas available to the connected workspace, optionally including each full | | **List standardizations** `docupipe_list_standardizations` | List structured extraction results, filtered by schema, document, or up to 1000 known | | **Create schema** `docupipe_create_schema` | Create a reusable extraction schema from a valid JSON Schema and optional extraction guidelines | | **Standardize document** `docupipe_standardize_document` | Start V3 agentic structured extraction for one processed document and return the job and | | **Upload document** `docupipe_upload_document` | Submit one local file or remote file URL for asynchronous parsing | ## Example prompts **Find Documents** > Use DocuPipe to find documents and walk me through the result in plain English. **Find Jobs** > Use DocuPipe to find jobs and walk me through the result in plain English. **Get Account Usage** > Pull the relevant data from DocuPipe, summarize it in plain English, and point out anything that needs attention. **Get Document** > Pull the relevant data from DocuPipe, 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 DocuPipe working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the DocuPipe API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected DocuPipe 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 DocuPipe. | 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 DocuPipe actions to the runtime in a format your agent can reliably use. | 13 tools for DocuPipe are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes DocuPipe 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 DocuPipe in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the DocuPipe 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 DocuPipe skill but can't call the tools The ClawHub skill teaches OpenClaw about DocuPipe, but the calls run through the ClawLink plugin and your connected account. Make sure DocuPipe 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 DocuPipe 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 DocuPipe tools DocuPipe 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 DocuPipe 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. ### DocuPipe 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 DocuPipe has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw DocuPipe integration? Yes. ClawLink is the fastest way to connect OpenClaw to DocuPipe: link your DocuPipe account once in the browser and OpenClaw can call the DocuPipe API through 13 ready-made tools — no custom code or token handling. ### How do I add DocuPipe to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink DocuPipe skill from ClawHub, then you click Connect in the dashboard to authorize DocuPipe. OpenClaw calls the tools from the next message — no config files, and the DocuPipe key you paste is stored server-side instead of in your environment. ### How long does it take to connect DocuPipe to OpenClaw? About two minutes. Sign in, click Connect next to DocuPipe in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring DocuPipe 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 DocuPipe working from chat. ### OpenClaw installed the DocuPipe skill but can't call the tools The ClawHub skill teaches OpenClaw about DocuPipe, but the calls run through the ClawLink plugin and your connected account. Make sure DocuPipe 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. - [Chatbotkit tools](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.