# How to connect Docmosis to OpenClaw (paste one key, 17 tools) > Connect Docmosis to OpenClaw with ClawLink: paste your Docmosis key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/docmosis The usual route to Docmosis 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 Docmosis setup: install one ClawHub skill, connect Docmosis in the browser, and OpenClaw can call real Docmosis 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 Docmosis. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Docmosis** — 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 docmosis # connect Docmosis (browser OAuth) npx -y @useclawlink/cli actions docmosis # list available actions npx -y @useclawlink/cli run docmosis --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 Docmosis in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Docmosis API key once. Verify the connection by asking OpenClaw: > Use Docmosis to environment ready 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 Docmosis is connected in the dashboard, that agent calls the same 17 Docmosis 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). ## Docmosis MCP for OpenClaw Looking for a Docmosis MCP server for OpenClaw? ClawLink connects Docmosis to OpenClaw and exposes 17 Docmosis 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 Docmosis integration](https://claw-link.dev/hermes/docmosis) works the same way. ## What the OpenClaw Docmosis integration can do 17 Docmosis tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 17. ### 15 of 17 Docmosis tools for OpenClaw | Tool | What it does | |---|---| | **Environment ready** `docmosis_environment_ready` | Verify environment readiness | | **Environment summary** `docmosis_environment_summary` | Retrieve environment summary | | **Get API key** `docmosis_get_api_key` | Extract the Docmosis API access key from connection metadata | | **Get batch upload status** `docmosis_get_batch_upload_status` | Check the status of a template batch upload job | | **Get image** `docmosis_get_image` | Download one or more images | | **Get render queue** `docmosis_get_render_queue` | Get current render queue status and utilization | | **Get render tags** `docmosis_get_render_tags` | Retrieve statistics on renders tagged with user-defined phrases | | **Get sample data** `docmosis_get_sample_data` | Generate sample data for a Docmosis template based on its structure | | **Get template** `docmosis_get_template` | Retrieve originally uploaded templates | | **Get template details** `docmosis_get_template_details` | Retrieve metadata for an uploaded template | | **Get template structure** `docmosis_get_template_structure` | Retrieve a template's parsed structure: fields, repeats, conditions, images, and refs | | **List images** `docmosis_list_images` | List available stock images | | **List templates** `docmosis_list_templates` | List all templates available in the environment | | **Ping** `docmosis_ping` | Check connectivity to Docmosis Cloud services | | **Ping docmosis service** `docmosis_ping_docmosis_service` | Check that Docmosis Cloud services are online and at least one server is listening | ## Example prompts **Environment Ready** > Use Docmosis to environment ready and walk me through the result in plain English. **Environment Summary** > Use Docmosis to environment summary and walk me through the result in plain English. **Get Api Key** > Pull the relevant data from Docmosis, summarize it in plain English, and point out anything that needs attention. **Get Batch Upload Status** > Pull the relevant data from Docmosis, 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 Docmosis working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Docmosis API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Docmosis 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 Docmosis. | 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 Docmosis actions to the runtime in a format your agent can reliably use. | 17 tools for Docmosis are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Docmosis 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 Docmosis in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Docmosis 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 Docmosis skill but can't call the tools The ClawHub skill teaches OpenClaw about Docmosis, but the calls run through the ClawLink plugin and your connected account. Make sure Docmosis 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 Docmosis 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 Docmosis tools Docmosis 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 Docmosis 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. ### Docmosis 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 Docmosis has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Docmosis integration? Yes. ClawLink is the fastest way to connect OpenClaw to Docmosis: link your Docmosis account once in the browser and OpenClaw can call the Docmosis API through 17 ready-made tools — no custom code or token handling. ### How do I add Docmosis to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Docmosis skill from ClawHub, then you click Connect in the dashboard to authorize Docmosis. OpenClaw calls the tools from the next message — no config files, and the Docmosis key you paste is stored server-side instead of in your environment. ### How long does it take to connect Docmosis to OpenClaw? About two minutes. Sign in, click Connect next to Docmosis in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Docmosis 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 Docmosis working from chat. ### OpenClaw installed the Docmosis skill but can't call the tools The ClawHub skill teaches OpenClaw about Docmosis, but the calls run through the ClawLink plugin and your connected account. Make sure Docmosis 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 GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.