# How to connect Craftmypdf to OpenClaw (paste one key, 12 tools)

> Connect Craftmypdf to OpenClaw with ClawLink: paste your Craftmypdf key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/craftmypdf

The usual route to Craftmypdf 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 Craftmypdf setup: install one ClawHub skill, connect Craftmypdf in the browser, and OpenClaw can call real Craftmypdf 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 Craftmypdf.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Craftmypdf** — 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 craftmypdf  # connect Craftmypdf (browser OAuth)
npx -y @useclawlink/cli actions craftmypdf  # list available actions
npx -y @useclawlink/cli run craftmypdf <action> --input '<json>'  # 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 Craftmypdf in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Craftmypdf API key once.

Verify the connection by asking OpenClaw:

> Pull the relevant data from Craftmypdf, 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:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Craftmypdf is connected in the dashboard, that agent calls the same 12 Craftmypdf 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).

## Craftmypdf MCP for OpenClaw

Looking for a Craftmypdf MCP server for OpenClaw? ClawLink connects Craftmypdf to OpenClaw and exposes 12 Craftmypdf 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 Craftmypdf integration](https://claw-link.dev/hermes/craftmypdf) works the same way.

## What the OpenClaw Craftmypdf integration can do

12 Craftmypdf tools are ready for OpenClaw once the account is connected.

### All 12 Craftmypdf tools for OpenClaw

| Tool | What it does |
|---|---|
| **Get account info** `craftmypdf_get_account_info` | Retrieve account information including subscription and usage details |
| **Get PDF info** `craftmypdf_get_pdf_info` | Retrieve information about a PDF file including metadata, page count, and other properties |
| **List templates** `craftmypdf_list_templates` | Retrieve a paginated list of PDF templates |
| **List transactions** `craftmypdf_list_transactions` | Retrieve a paginated list of API transactions |
| **Query template usage** `craftmypdf_query_template_usage` | Retrieve usage statistics for specified templates within a date range |
| **Add text to PDF** `craftmypdf_add_text_to_pdf` | Add text annotations to a PDF including page numbers, watermarks, and custom text at specified |
| **Add watermark** `craftmypdf_add_watermark` | Add a text watermark to a PDF with customizable font, size, color, opacity, and rotation |
| **Create editor session** `craftmypdf_create_editor_session` | Create an embeddable editor session URL for a template |
| **Create PDF async2** `craftmypdf_create_pdf_async2` | Create a PDF file asynchronously with JSON data and template |
| **Create PDF parallel** `craftmypdf_create_pdf_parallel` | Create multiple PDF files in parallel from templates with JSON data |
| **Merge pdfs** `craftmypdf_merge_pdfs` | Merge multiple PDF files from URLs into a single PDF document |
| **Update PDF fields** `craftmypdf_update_pdf_fields` | Update fillable fields in a PDF document such as text fields, checkboxes, and dropdowns |

## Example prompts

**Get Account Info**

> Pull the relevant data from Craftmypdf, summarize it in plain English, and point out anything that needs attention.

**Get Pdf Info**

> Pull the relevant data from Craftmypdf, summarize it in plain English, and point out anything that needs attention.

**List Templates**

> List the relevant items in Craftmypdf, group them by priority, and recommend what OpenClaw should do next.

**List Transactions**

> List the relevant items in Craftmypdf, 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 Craftmypdf working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Craftmypdf API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Craftmypdf 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 Craftmypdf. | 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 Craftmypdf actions to the runtime in a format your agent can reliably use. | 12 tools for Craftmypdf are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Craftmypdf 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 Craftmypdf in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Craftmypdf 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 Craftmypdf skill but can't call the tools
The ClawHub skill teaches OpenClaw about Craftmypdf, but the calls run through the ClawLink plugin and your connected account. Make sure Craftmypdf 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 Craftmypdf 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 Craftmypdf tools
Craftmypdf 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 Craftmypdf 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.

### Craftmypdf 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 Craftmypdf has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Craftmypdf integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Craftmypdf: link your Craftmypdf account once in the browser and OpenClaw can call the Craftmypdf API through 12 ready-made tools — no custom code or token handling.

### How do I add Craftmypdf to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Craftmypdf skill from ClawHub, then you click Connect in the dashboard to authorize Craftmypdf. OpenClaw calls the tools from the next message — no config files, and the Craftmypdf key you paste is stored server-side instead of in your environment.

### How long does it take to connect Craftmypdf to OpenClaw?
About two minutes. Sign in, click Connect next to Craftmypdf in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Craftmypdf 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 Craftmypdf working from chat.

### OpenClaw installed the Craftmypdf skill but can't call the tools
The ClawHub skill teaches OpenClaw about Craftmypdf, but the calls run through the ClawLink plugin and your connected account. Make sure Craftmypdf 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 GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows
- [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services
- [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.
