How to connect iLovePDF to OpenClaw
Connect iLovePDF to OpenClaw with ClawLink: paste your iLovePDF key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
iLovePDFAPI KEYMCPiLovePDF provides APIs for processing, converting, optimizing, and signing PDF and image files.. Once connected, OpenClaw can read and act on iLovePDF from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to iLovePDF 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 iLovePDF setup: install one ClawHub skill, connect iLovePDF in the browser, and OpenClaw can call real iLovePDF 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 iLovePDF.
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 iLovePDF
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with iLovePDF?"
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 iLovePDF in the ClawLink dashboard — paste your iLovePDF API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from iLovePDF, summarize it in plain English, and point out anything that needs attention.
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 iLovePDF is connected in the dashboard, that agent calls the same 9 iLovePDF tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
iLovePDF MCP for OpenClaw
Looking for a iLovePDF MCP server for OpenClaw? ClawLink connects iLovePDF to OpenClaw and exposes 9 iLovePDF tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes iLovePDF integration works the same way.
What the OpenClaw iLovePDF integration can do
9 iLovePDF 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 iLovePDF tools for OpenClaw
| Tool | What it does |
|---|---|
Get account info i_love_pdf_get_account_info | Return the connected iLovePDF project's account type and remaining processing allowance |
Get task status i_love_pdf_get_task_status | Inspect an iLovePDF task's current state and output metadata on its assigned worker |
Compress images i_love_pdf_compress_images | Compress one or more images and immediately return the resulting image or ZIP as an offloaded |
Compress pdfs i_love_pdf_compress_pdfs | Compress one or more PDFs and return the stored PDF or ZIP output in one workflow: task |
Convert images to PDF i_love_pdf_convert_images_to_pdf | Convert one or more images into PDF output using iLovePDF's documented defaults and immediately |
Convert PDF to images i_love_pdf_convert_pdf_to_images | Convert a PDF using iLovePDF's default PDF-to-JPG behavior and immediately return the generated |
Merge pdfs i_love_pdf_merge_pdfs | Merge two or more PDFs in the supplied order and return the merged file in one workflow |
Split PDF i_love_pdf_split_pdf | Split one PDF by explicit ranges, fixed page intervals, or removed pages and return the |
Try it: find the iLovePDF tool you need
Browse the 8 iLovePDF tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from iLovePDF, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from iLovePDF, summarize it in plain English, and point out anything that needs attention.
Use iLovePDF to compress images and walk me through the result in plain English.
Use iLovePDF to compress pdfs 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 iLovePDF working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the iLovePDF API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected iLovePDF 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 iLovePDF. | 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 iLovePDF actions to the runtime in a format your agent can reliably use. | 9 tools for iLovePDF are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes iLovePDF 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 iLovePDF in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the iLovePDF 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 iLovePDF skill but can't call the tools
The ClawHub skill teaches OpenClaw about iLovePDF, but the calls run through the ClawLink plugin and your connected account. Make sure iLovePDF 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 iLovePDF 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 iLovePDF tools
iLovePDF 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 iLovePDF 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.
iLovePDF 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 iLovePDF 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 iLovePDF integration?
Yes. ClawLink is the fastest way to connect OpenClaw to iLovePDF: link your iLovePDF account once in the browser and OpenClaw can call the iLovePDF API through 9 ready-made tools — no custom code or token handling.
How do I add iLovePDF to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink iLovePDF skill from ClawHub, then you click Connect in the dashboard to authorize iLovePDF. OpenClaw calls the tools from the next message — no config files, and the iLovePDF key you paste is stored server-side instead of in your environment.
How long does it take to connect iLovePDF to OpenClaw?
About two minutes. Sign in, click Connect next to iLovePDF in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring iLovePDF 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 iLovePDF working from chat.
OpenClaw installed the iLovePDF skill but can't call the tools
The ClawHub skill teaches OpenClaw about iLovePDF, but the calls run through the ClawLink plugin and your connected account. Make sure iLovePDF 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.
