# How to connect PDFMonkey to OpenClaw (paste one key, 18 tools) > Connect PDFMonkey to OpenClaw with ClawLink: paste your PDFMonkey key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/pdfmonkey The usual route to PDFMonkey 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 PDFMonkey setup: install one ClawHub skill, connect PDFMonkey in the browser, and OpenClaw can call real PDFMonkey 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 PDFMonkey. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect PDFMonkey** — 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 pdfmonkey # connect PDFMonkey (browser OAuth) npx -y @useclawlink/cli actions pdfmonkey # list available actions npx -y @useclawlink/cli run pdfmonkey --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 PDFMonkey in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PDFMonkey API key once. Verify the connection by asking OpenClaw: > Use PDFMonkey to download document 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once PDFMonkey is connected in the dashboard, that agent calls the same 18 PDFMonkey 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). ## PDFMonkey MCP for OpenClaw Looking for a PDFMonkey MCP server for OpenClaw? ClawLink connects PDFMonkey to OpenClaw and exposes 18 PDFMonkey 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 PDFMonkey integration](https://claw-link.dev/hermes/pdfmonkey) works the same way. ## What the OpenClaw PDFMonkey integration can do 18 PDFMonkey tools are ready for OpenClaw once the account is connected. The 16 below are the ones people reach for most; your agent can call all 18. ### 16 of 18 PDFMonkey tools for OpenClaw | Tool | What it does | |---|---| | **Download document file** `pdfmonkey_download_document_file` | Download a generated PDF file via a presigned URL | | **Get current user** `pdfmonkey_get_current_user` | Retrieve details about the currently authenticated user | | **Get document** `pdfmonkey_get_document` | Fetch a Document by its ID | | **Get document card** `pdfmonkey_get_document_card` | Fetch a DocumentCard by ID | | **Get template** `pdfmonkey_get_template` | Fetch a Document Template by ID | | **List document cards** `pdfmonkey_list_document_cards` | List DocumentCards | | **List PDF engines** `pdfmonkey_list_pdf_engines` | Lists all available PDF rendering engines in PDFMonkey | | **List templates** `pdfmonkey_list_templates` | List all document template cards for a workspace | | **List workspaces** `pdfmonkey_list_workspaces` | List workspaces (applications) | | **Preview template** `pdfmonkey_preview_template` | Fetches the template preview viewer page from PDFMonkey's preview_url | | **View public share link** `pdfmonkey_view_public_share_link` | Download a publicly shared PDF via its permanent share link | | **Create document** `pdfmonkey_create_document` | Create a Document | | **Create document sync** `pdfmonkey_create_document_sync` | Create a document and wait for generation to finish | | **Create template** `pdfmonkey_create_template` | Creates a new PDF document template in PDFMonkey | | **Update document** `pdfmonkey_update_document` | Updates an existing PDFMonkey document's payload, metadata, template, or status | | **Update template** `pdfmonkey_update_template` | Update a document template’s properties | ## Example prompts **Download Document File** > Use PDFMonkey to download document file and walk me through the result in plain English. **Get Current User** > Pull the relevant data from PDFMonkey, summarize it in plain English, and point out anything that needs attention. **Get Document** > Pull the relevant data from PDFMonkey, summarize it in plain English, and point out anything that needs attention. **Get Document Card** > Pull the relevant data from PDFMonkey, 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 PDFMonkey working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PDFMonkey API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PDFMonkey 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 PDFMonkey. | 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 PDFMonkey actions to the runtime in a format your agent can reliably use. | 18 tools for PDFMonkey are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PDFMonkey 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 PDFMonkey in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the PDFMonkey 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 PDFMonkey skill but can't call the tools The ClawHub skill teaches OpenClaw about PDFMonkey, but the calls run through the ClawLink plugin and your connected account. Make sure PDFMonkey 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 PDFMonkey 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 PDFMonkey tools PDFMonkey 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 PDFMonkey 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. ### PDFMonkey 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 PDFMonkey has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw PDFMonkey integration? Yes. ClawLink is the fastest way to connect OpenClaw to PDFMonkey: link your PDFMonkey account once in the browser and OpenClaw can call the PDFMonkey API through 18 ready-made tools — no custom code or token handling. ### How do I add PDFMonkey to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PDFMonkey skill from ClawHub, then you click Connect in the dashboard to authorize PDFMonkey. OpenClaw calls the tools from the next message — no config files, and the PDFMonkey key you paste is stored server-side instead of in your environment. ### How long does it take to connect PDFMonkey to OpenClaw? About two minutes. Sign in, click Connect next to PDFMonkey in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring PDFMonkey 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 PDFMonkey working from chat. ### OpenClaw installed the PDFMonkey skill but can't call the tools The ClawHub skill teaches OpenClaw about PDFMonkey, but the calls run through the ClawLink plugin and your connected account. Make sure PDFMonkey 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.