How to connect Conversion Tools to OpenClaw
Connect Conversion Tools to OpenClaw with ClawLink: paste your Conversion Tools key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine.
Conversion ToolsAPI KEYMCPConversion Tools is an online service that offers a fast and easy way to convert documents between different formats, like XML, Excel, PDF, Word, Text, CSV, and others.. Once connected, OpenClaw can read and act on Conversion Tools from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Conversion Tools 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 Conversion Tools setup: install one ClawHub skill, connect Conversion Tools in the browser, and OpenClaw can call real Conversion Tools 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 Conversion Tools.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Conversion Tools
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Conversion Tools?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Conversion Tools in the ClawLink dashboard — paste your Conversion Tools API key once.
Verify the connection by asking OpenClaw:
Use Conversion Tools to download file 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Conversion Tools is connected in the dashboard, that agent calls the same 11 Conversion Tools tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Conversion Tools MCP for OpenClaw
Looking for a Conversion Tools MCP server for OpenClaw? ClawLink connects Conversion Tools to OpenClaw and exposes 11 Conversion Tools tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Conversion Tools integration works the same way.
What the OpenClaw Conversion Tools integration can do
11 Conversion Tools tools are ready for OpenClaw once the account is connected.
All 11 Conversion Tools tools for OpenClaw
| Tool | What it does |
|---|---|
Download file conversion_tools_download_file | Download a converted file from the Conversion Tools API using its file ID |
Get auth info conversion_tools_get_auth_info | Get information about the authenticated user including email address |
Get config conversion_tools_get_config | Get available conversion types and their configuration |
Get file info conversion_tools_get_file_info | Get metadata about a file including size, name, and preview (for text files) |
Get task status conversion_tools_get_task_status | Get the status of a conversion task |
List tasks conversion_tools_list_tasks | Get all tasks for the authenticated user (up to 50 most recent tasks) |
Convert excel to HTML conversion_tools_convert_excel_to_html | Convert an Excel (.xlsx) file to HTML table format |
Convert word to text conversion_tools_convert_word_to_text | Convert Word documents (.doc/.docx) to plain text (.txt) |
Create task conversion_tools_create_task | Create a new conversion task |
Update task retention conversion_tools_update_task_retention | Update the retention mode for a task |
Upload file conversion_tools_upload_file | Upload a file to the ConversionTools API for subsequent conversion operations |
Try it: find the Conversion Tools tool you need
Browse the 11 Conversion Tools tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Conversion Tools to download file and walk me through the result in plain English.
Pull the relevant data from Conversion Tools, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Conversion Tools, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Conversion Tools, 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 Conversion Tools working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Conversion Tools API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Conversion Tools 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 Conversion Tools. | 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 Conversion Tools actions to the runtime in a format your agent can reliably use. | 11 tools for Conversion Tools are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Conversion Tools 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 Conversion Tools in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Conversion Tools key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Conversion Tools skill but can't call the tools
The ClawHub skill teaches OpenClaw about Conversion Tools, but the calls run through the ClawLink plugin and your connected account. Make sure Conversion Tools 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 Conversion Tools 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 Conversion Tools tools
Conversion Tools 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 Conversion Tools 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.
Conversion Tools 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 Conversion Tools has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Conversion Tools integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Conversion Tools: link your Conversion Tools account once in the browser and OpenClaw can call the Conversion Tools API through 11 ready-made tools — no custom code or token handling.
How do I add Conversion Tools to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Conversion Tools skill from ClawHub, then you click Connect in the dashboard to authorize Conversion Tools. OpenClaw calls the tools from the next message — no config files, and the Conversion Tools key you paste is stored server-side instead of in your environment.
How long does it take to connect Conversion Tools to OpenClaw?
About two minutes. Sign in, click Connect next to Conversion Tools in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Conversion Tools 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 Conversion Tools working from chat.
OpenClaw installed the Conversion Tools skill but can't call the tools
The ClawHub skill teaches OpenClaw about Conversion Tools, but the calls run through the ClawLink plugin and your connected account. Make sure Conversion Tools 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.
