How to connect CloudConvert to OpenClaw
Connect CloudConvert to OpenClaw with ClawLink: paste your CloudConvert key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
CloudConvertAPI KEYMCPCloudConvert is a file conversion service supporting over 200 formats, including audio, video, document, ebook, archive, image, spreadsheet, and presentation formats.. Once connected, OpenClaw can read and act on CloudConvert from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to CloudConvert 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 CloudConvert setup: install one ClawHub skill, connect CloudConvert in the browser, and OpenClaw can call real CloudConvert 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 CloudConvert.
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 CloudConvert
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with CloudConvert?"
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 CloudConvert in the ClawLink dashboard — paste your CloudConvert API key once.
Verify the connection by asking OpenClaw:
List the relevant items in CloudConvert, group them by priority, and recommend what OpenClaw should do next.
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 CloudConvert is connected in the dashboard, that agent calls the same 9 CloudConvert tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
CloudConvert MCP for OpenClaw
Looking for a CloudConvert MCP server for OpenClaw? ClawLink connects CloudConvert to OpenClaw and exposes 9 CloudConvert tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes CloudConvert integration works the same way.
What the OpenClaw CloudConvert integration can do
9 CloudConvert tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9.
8 of 9 CloudConvert tools for OpenClaw
| Tool | What it does |
|---|---|
List operations cloudconvert_list_operations | List all possible CloudConvert operations with their available options and engine details |
List supported formats cloudconvert_list_supported_formats | List all supported conversion formats, engines, and options |
List tasks cloudconvert_list_tasks | List all CloudConvert tasks with their status, payload and results |
List webhooks cloudconvert_list_webhooks | List all webhooks |
Show user cloudconvert_show_user | Retrieves the current authenticated user's CloudConvert account information |
Create export google cloud storage task cloudconvert_create_export_google_cloud_storage_task | Create a task to export files to a Google Cloud Storage bucket |
Create export s3 task cloudconvert_create_export_s3_task | Create a task to export files to an Amazon S3 bucket |
Create webhook cloudconvert_create_webhook | Creates a new webhook to receive CloudConvert event notifications |
Try it: find the CloudConvert tool you need
Browse the 8 CloudConvert tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
List the relevant items in CloudConvert, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in CloudConvert, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in CloudConvert, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in CloudConvert, group them by priority, and recommend what OpenClaw should do next.
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 CloudConvert working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the CloudConvert API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CloudConvert 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 CloudConvert. | 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 CloudConvert actions to the runtime in a format your agent can reliably use. | 9 tools for CloudConvert are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes CloudConvert 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 CloudConvert in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the CloudConvert 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 CloudConvert skill but can't call the tools
The ClawHub skill teaches OpenClaw about CloudConvert, but the calls run through the ClawLink plugin and your connected account. Make sure CloudConvert 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 CloudConvert 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 CloudConvert tools
CloudConvert 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 CloudConvert 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.
CloudConvert 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 CloudConvert 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 CloudConvert integration?
Yes. ClawLink is the fastest way to connect OpenClaw to CloudConvert: link your CloudConvert account once in the browser and OpenClaw can call the CloudConvert API through 9 ready-made tools — no custom code or token handling.
How do I add CloudConvert to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink CloudConvert skill from ClawHub, then you click Connect in the dashboard to authorize CloudConvert. OpenClaw calls the tools from the next message — no config files, and the CloudConvert key you paste is stored server-side instead of in your environment.
How long does it take to connect CloudConvert to OpenClaw?
About two minutes. Sign in, click Connect next to CloudConvert in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring CloudConvert 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 CloudConvert working from chat.
OpenClaw installed the CloudConvert skill but can't call the tools
The ClawHub skill teaches OpenClaw about CloudConvert, but the calls run through the ClawLink plugin and your connected account. Make sure CloudConvert 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.
