# How to connect Intelliprint to OpenClaw (paste one key, 21 tools) > Connect Intelliprint to OpenClaw with ClawLink: paste your Intelliprint key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/intelliprint The usual route to Intelliprint 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 Intelliprint setup: install one ClawHub skill, connect Intelliprint in the browser, and OpenClaw can call real Intelliprint 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 Intelliprint. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Intelliprint** — 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 intelliprint # connect Intelliprint (browser OAuth) npx -y @useclawlink/cli actions intelliprint # list available actions npx -y @useclawlink/cli run intelliprint --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 Intelliprint in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Intelliprint API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Intelliprint, 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 Intelliprint is connected in the dashboard, that agent calls the same 21 Intelliprint 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). ## Intelliprint MCP for OpenClaw Looking for a Intelliprint MCP server for OpenClaw? ClawLink connects Intelliprint to OpenClaw and exposes 21 Intelliprint 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 Intelliprint integration](https://claw-link.dev/hermes/intelliprint) works the same way. ## What the OpenClaw Intelliprint integration can do 21 Intelliprint tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 21. ### 17 of 21 Intelliprint tools for OpenClaw | Tool | What it does | |---|---| | **Get mailing list** `intelliprint_get_mailing_list` | Retrieve a single mailing list by its ID | | **Get mailing list recipient** `intelliprint_get_mailing_list_recipient` | Retrieve a single recipient by ID within a specified mailing list | | **List backgrounds** `intelliprint_list_backgrounds` | List backgrounds with optional filtering and pagination | | **List mailing list recipients** `intelliprint_list_mailing_list_recipients` | List all recipients in a mailing list with pagination and sorting options | | **List mailing lists** `intelliprint_list_mailing_lists` | List all available mailing lists with pagination and sorting options | | **List print jobs** `intelliprint_list_print_jobs` | List print jobs with optional filters and pagination | | **List templates** `intelliprint_list_templates` | List all available templates | | **Retrieve background** `intelliprint_retrieve_background` | Retrieve a specific Background by ID | | **Retrieve print job** `intelliprint_retrieve_print_job` | Retrieve details of a Print Job by its ID | | **Create background** `intelliprint_create_background` | Create a new Background by uploading a PDF file | | **Create mailing list** `intelliprint_create_mailing_list` | Create a mailing list to store thousands of recipients and send mail items to all of them at | | **Create mailing list recipient** `intelliprint_create_mailing_list_recipient` | Create a new recipient within a mailing list | | **Create print job** `intelliprint_create_print_job` | Create a new print job in Intelliprint by uploading a document | | **Merge files** `intelliprint_merge_files` | Merges multiple PDF, RTF, or Word documents into a single PDF file | | **Update background** `intelliprint_update_background` | Update an existing Background's name or team | | **Update mailing list** `intelliprint_update_mailing_list` | Update a mailing list | | **Update mailing list recipient** `intelliprint_update_mailing_list_recipient` | Update an existing recipient in a mailing list by ID | ## Example prompts **Get Mailing List** > Pull the relevant data from Intelliprint, summarize it in plain English, and point out anything that needs attention. **Get Mailing List Recipient** > Pull the relevant data from Intelliprint, summarize it in plain English, and point out anything that needs attention. **List Backgrounds** > List the relevant items in Intelliprint, group them by priority, and recommend what OpenClaw should do next. **List Mailing List Recipients** > List the relevant items in Intelliprint, 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 Intelliprint working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Intelliprint API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Intelliprint 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 Intelliprint. | 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 Intelliprint actions to the runtime in a format your agent can reliably use. | 21 tools for Intelliprint are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Intelliprint 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 Intelliprint in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Intelliprint 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 Intelliprint skill but can't call the tools The ClawHub skill teaches OpenClaw about Intelliprint, but the calls run through the ClawLink plugin and your connected account. Make sure Intelliprint 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 Intelliprint 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 Intelliprint tools Intelliprint 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 Intelliprint 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. ### Intelliprint 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 Intelliprint has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Intelliprint integration? Yes. ClawLink is the fastest way to connect OpenClaw to Intelliprint: link your Intelliprint account once in the browser and OpenClaw can call the Intelliprint API through 21 ready-made tools — no custom code or token handling. ### How do I add Intelliprint to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Intelliprint skill from ClawHub, then you click Connect in the dashboard to authorize Intelliprint. OpenClaw calls the tools from the next message — no config files, and the Intelliprint key you paste is stored server-side instead of in your environment. ### How long does it take to connect Intelliprint to OpenClaw? About two minutes. Sign in, click Connect next to Intelliprint in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Intelliprint 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 Intelliprint working from chat. ### OpenClaw installed the Intelliprint skill but can't call the tools The ClawHub skill teaches OpenClaw about Intelliprint, but the calls run through the ClawLink plugin and your connected account. Make sure Intelliprint 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 - [Connect PagerDuty](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.