How to connect PDF.co to OpenClaw
Connect PDF.co to OpenClaw with ClawLink: paste your PDF.co key once and 34 tools work from chat. No MCP server to run, nothing stored on your machine.


PDF.co is a REST API platform for PDF automation including PDF extraction, generation, editing, splitting, merging, form filling, barcode processing, OCR, document parsing, file conversion (PDF to Excel/CSV/JSON/XML/HTML/Image and vice versa), and AI-powered invoice parsing.. Once connected, OpenClaw can read and act on PDF.co from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to PDF.co 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 PDF.co setup: install one ClawHub skill, connect PDF.co in the browser, and OpenClaw can call real PDF.co 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 PDF.co.
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 PDF.co
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with PDF.co?"
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 PDF.co in the ClawLink dashboard — paste your PDF.co API key once.
Verify the connection by asking OpenClaw:
Use PDF.co to account balance info 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 PDF.co is connected in the dashboard, that agent calls the same 34 PDF.co tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
PDF.co MCP for OpenClaw
Looking for a PDF.co MCP server for OpenClaw? ClawLink connects PDF.co to OpenClaw and exposes 34 PDF.co tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes PDF.co integration works the same way.
What the OpenClaw PDF.co integration can do
34 PDF.co tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 34.
30 of 34 PDF.co tools for OpenClaw
| Tool | What it does |
|---|---|
Account balance info pdf_co_account_balance_info | Get account balance info |
Convert excel to text pdf_co_convert_excel_to_text | Convert Excel files to plain text |
Convert excel to xml pdf_co_convert_excel_to_xml | Convert an Excel file to XML |
Document parser pdf_co_document_parser | Parse documents based on predefined templates to extract structured data |
Job check pdf_co_job_check | Check status and result of an asynchronous job |
PDF extract attachments pdf_co_pdf_extract_attachments | Extract embedded attachments from a PDF |
PDF find pdf_co_pdf_find | Find text in a PDF document |
PDF forms info reader pdf_co_pdf_forms_info_reader | Extract form field information from a PDF |
PDF info reader pdf_co_pdf_info_reader | Retrieve detailed information and metadata of a PDF |
PDF rotate pdf_co_pdf_rotate | Rotate selected pages in a PDF |
PDF split pdf_co_pdf_split | Split a PDF into multiple files by page ranges |
PDF to image pdf_co_pdf_to_image | Convert PDF pages to images (PNG, JPG, TIFF) |
PDF to json pdf_co_pdf_to_json | Convert PDF or scanned images to JSON format |
PDF to xls pdf_co_pdf_to_xls | Convert PDF or scanned images to XLS format |
PDF to xml pdf_co_pdf_to_xml | Convert PDF or scanned images to XML format |
Convert excel to CSV pdf_co_convert_excel_to_csv | Convert an Excel file (XLS/XLSX) to CSV |
Convert excel to HTML pdf_co_convert_excel_to_html | Convert an Excel file to HTML |
Convert excel to json pdf_co_convert_excel_to_json | Convert an online Excel or CSV file to JSON format |
File upload pdf_co_file_upload | Upload a local file or remote URL to PDF.co, returning a hosted URL for downstream processing |
PDF add pdf_co_pdf_add | Add content to an existing PDF |
PDF change text searchable pdf_co_pdf_change_text_searchable | Make PDF text searchable using OCR |
PDF from document txt pdf_co_pdf_from_document_txt | Convert a plain text (.txt) file to PDF |
PDF from email pdf_co_pdf_from_email | Convert email files (.eml/.msg) to PDF |
PDF from HTML pdf_co_pdf_from_html | Convert HTML code or webpage URL into a PDF document |
PDF merge pdf_co_pdf_merge | Merge multiple PDF files into one document |
PDF search and replace text pdf_co_pdf_search_and_replace_text | Search for and replace text in a PDF document |
PDF to CSV pdf_co_pdf_to_csv | Convert PDF or scanned images to CSV format |
PDF to HTML pdf_co_pdf_to_html | Convert PDF documents to HTML |
PDF to text pdf_co_pdf_to_text | Convert PDF or scanned images to plain text |
PDF to xlsx pdf_co_pdf_to_xlsx | Convert PDF or scanned images to XLSX (Excel) format |
Try it: find the PDF.co tool you need
Browse the 30 PDF.co tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use PDF.co to account balance info and walk me through the result in plain English.
Use PDF.co to convert excel to text and walk me through the result in plain English.
Use PDF.co to convert excel to xml and walk me through the result in plain English.
Use PDF.co to document parser 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 PDF.co working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the PDF.co API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PDF.co 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 PDF.co. | 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 PDF.co actions to the runtime in a format your agent can reliably use. | 34 tools for PDF.co are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes PDF.co 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 PDF.co in the browser, and the 34 tools above work from chat. There is no SDK and no config file, and the PDF.co 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 PDF.co skill but can't call the tools
The ClawHub skill teaches OpenClaw about PDF.co, but the calls run through the ClawLink plugin and your connected account. Make sure PDF.co 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 PDF.co 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 PDF.co tools
PDF.co 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 PDF.co 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.
PDF.co 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 PDF.co 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 PDF.co integration?
Yes. ClawLink is the fastest way to connect OpenClaw to PDF.co: link your PDF.co account once in the browser and OpenClaw can call the PDF.co API through 34 ready-made tools — no custom code or token handling.
How do I add PDF.co to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PDF.co skill from ClawHub, then you click Connect in the dashboard to authorize PDF.co. OpenClaw calls the tools from the next message — no config files, and the PDF.co key you paste is stored server-side instead of in your environment.
How long does it take to connect PDF.co to OpenClaw?
About two minutes. Sign in, click Connect next to PDF.co in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring PDF.co 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 PDF.co working from chat.
OpenClaw installed the PDF.co skill but can't call the tools
The ClawHub skill teaches OpenClaw about PDF.co, but the calls run through the ClawLink plugin and your connected account. Make sure PDF.co 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
DataRobot
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
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.
OpenClaw Just One API integration
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.