# How to connect Convertapi to OpenClaw (paste one key, 17 tools) > Connect Convertapi to OpenClaw with ClawLink: paste your Convertapi 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/convertapi The usual route to Convertapi 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 Convertapi setup: install one ClawHub skill, connect Convertapi in the browser, and OpenClaw can call real Convertapi 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 Convertapi. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Convertapi** — 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 convertapi # connect Convertapi (browser OAuth) npx -y @useclawlink/cli actions convertapi # list available actions npx -y @useclawlink/cli run convertapi --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 Convertapi in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Convertapi API key once. Verify the connection by asking OpenClaw: > Use Convertapi to check conversion support 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 Convertapi is connected in the dashboard, that agent calls the same 17 Convertapi 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). ## Convertapi MCP for OpenClaw Looking for a Convertapi MCP server for OpenClaw? ClawLink connects Convertapi to OpenClaw and exposes 17 Convertapi 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 Convertapi integration](https://claw-link.dev/hermes/convertapi) works the same way. ## What the OpenClaw Convertapi integration can do 17 Convertapi 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 Convertapi tools for OpenClaw | Tool | What it does | |---|---| | **Check conversion support** `convertapi_check_conversion_support` | Check whether a specific file format conversion is supported by ConvertAPI | | **Convert get supported input formats for output** `convertapi_convert_get_supported_input_formats_for_output` | Retrieves a complete list of input file formats that ConvertAPI can convert to a specified | | **Download file** `convertapi_download_file` | Download a converted or uploaded file from ConvertAPI server using its FileId | | **Download uploaded file** `convertapi_download_uploaded_file` | Download a previously uploaded file by its FileId | | **Get converter spec** `convertapi_get_converter_spec` | Retrieve the OpenAPI specification for a specific file conversion endpoint | | **Get file info** `convertapi_get_file_info` | Get metadata information about a stored file without downloading it | | **Get openapi schema** `convertapi_get_openapi_schema` | Retrieve the complete OpenAPI 3.0 specification for all ConvertAPI endpoints | | **Get supported output formats for input** `convertapi_get_supported_output_formats_for_input` | List all output formats a given input format can be converted into | | **Get user** `convertapi_get_user` | Get authenticated user account information including balance, conversions consumed, and | | **Get user statistics** `convertapi_get_user_statistics` | Retrieve usage statistics for the authenticated user account | | **List converters** `convertapi_list_converters` | Retrieve a comprehensive list of all available file converters in ConvertAPI | | **Async convert** `convertapi_async_convert` | Perform an asynchronous file conversion | | **Convert PDF to docx** `convertapi_convert_pdf_to_docx` | Convert PDF files to DOCX format | | **Convert PDF to jpg and store** `convertapi_convert_pdf_to_jpg_and_store` | Convert a PDF to JPG and store the result on the server | | **Convert upload file from URL** `convertapi_convert_upload_file_from_url` | Upload a file directly from a remote URL | ## Example prompts **Check Conversion Support** > Use Convertapi to check conversion support and walk me through the result in plain English. **Convert Get Supported Input Formats For Output** > Use Convertapi to convert get supported input formats for output and walk me through the result in plain English. **Download File** > Use Convertapi to download file and walk me through the result in plain English. **Download Uploaded File** > Use Convertapi to download uploaded file and walk me through the result in plain English. ## 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 Convertapi working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Convertapi API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Convertapi 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 Convertapi. | 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 Convertapi actions to the runtime in a format your agent can reliably use. | 17 tools for Convertapi are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Convertapi 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 Convertapi in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Convertapi 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 Convertapi skill but can't call the tools The ClawHub skill teaches OpenClaw about Convertapi, but the calls run through the ClawLink plugin and your connected account. Make sure Convertapi 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 Convertapi 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 Convertapi tools Convertapi 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 Convertapi 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. ### Convertapi 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 Convertapi has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Convertapi integration? Yes. ClawLink is the fastest way to connect OpenClaw to Convertapi: link your Convertapi account once in the browser and OpenClaw can call the Convertapi API through 17 ready-made tools — no custom code or token handling. ### How do I add Convertapi to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Convertapi skill from ClawHub, then you click Connect in the dashboard to authorize Convertapi. OpenClaw calls the tools from the next message — no config files, and the Convertapi key you paste is stored server-side instead of in your environment. ### How long does it take to connect Convertapi to OpenClaw? About two minutes. Sign in, click Connect next to Convertapi in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Convertapi 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 Convertapi working from chat. ### OpenClaw installed the Convertapi skill but can't call the tools The ClawHub skill teaches OpenClaw about Convertapi, but the calls run through the ClawLink plugin and your connected account. Make sure Convertapi 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 Box](https://claw-link.dev/openclaw/box) — Store, share, and manage files and folders - [Supabase tools](https://claw-link.dev/openclaw/supabase) — Query and manage Postgres databases - [Dropbox](https://claw-link.dev/openclaw/dropbox) — Store, sync, and share files