# How to connect Pneumatic to OpenClaw (paste one key, 10 tools) > Connect Pneumatic to OpenClaw with ClawLink: paste your Pneumatic key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/pneumatic The usual route to Pneumatic 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 Pneumatic setup: install one ClawHub skill, connect Pneumatic in the browser, and OpenClaw can call real Pneumatic 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 Pneumatic. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Pneumatic** — 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 pneumatic # connect Pneumatic (browser OAuth) npx -y @useclawlink/cli actions pneumatic # list available actions npx -y @useclawlink/cli run pneumatic --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 Pneumatic in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Pneumatic API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Pneumatic, 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 Pneumatic is connected in the dashboard, that agent calls the same 10 Pneumatic 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). ## Pneumatic MCP for OpenClaw Looking for a Pneumatic MCP server for OpenClaw? ClawLink connects Pneumatic to OpenClaw and exposes 10 Pneumatic 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 Pneumatic integration](https://claw-link.dev/hermes/pneumatic) works the same way. ## What the OpenClaw Pneumatic integration can do 10 Pneumatic tools are ready for OpenClaw once the account is connected. ### All 10 Pneumatic tools for OpenClaw | Tool | What it does | |---|---| | **Get task** `pneumatic_get_task` | Get one task's instructions, output fields, performers, checklists, due date, and completion | | **Get template** `pneumatic_get_template` | Get a workflow template's tasks, kickoff fields, owners, and execution settings before running | | **Get workflow** `pneumatic_get_workflow` | Get the current state, tasks, kickoff values, owners, and timing for one workflow run | | **List datasets** `pneumatic_list_datasets` | List reusable Pneumatic datasets available for workflow and template field configuration | | **List tasks** `pneumatic_list_tasks` | Find tasks assigned to the connected user or team, including active or completed work | | **List templates** `pneumatic_list_templates` | Find workflow templates the connected user can access, with filters for name, activity, and | | **List workflows** `pneumatic_list_workflows` | Find workflow runs by text, status, template, starter, current performer, or current task | | **Run template** `pneumatic_run_template` | Start a workflow from an accessible template, optionally supplying a name, urgency, due date | | **Save dataset** `pneumatic_save_dataset` | Create a reusable dataset or update an existing dataset's name, description, or ordered items | | **Set task completion** `pneumatic_set_task_completion` | Complete an active task with output values or revert a completed task back to active work | ## Example prompts **Get Task** > Pull the relevant data from Pneumatic, summarize it in plain English, and point out anything that needs attention. **Get Template** > Pull the relevant data from Pneumatic, summarize it in plain English, and point out anything that needs attention. **Get Workflow** > Pull the relevant data from Pneumatic, summarize it in plain English, and point out anything that needs attention. **List Datasets** > List the relevant items in Pneumatic, 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 Pneumatic working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Pneumatic API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Pneumatic 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 Pneumatic. | 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 Pneumatic actions to the runtime in a format your agent can reliably use. | 10 tools for Pneumatic are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Pneumatic 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 Pneumatic in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Pneumatic 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 Pneumatic skill but can't call the tools The ClawHub skill teaches OpenClaw about Pneumatic, but the calls run through the ClawLink plugin and your connected account. Make sure Pneumatic 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 Pneumatic 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 Pneumatic tools Pneumatic 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 Pneumatic 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. ### Pneumatic 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 Pneumatic has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Pneumatic integration? Yes. ClawLink is the fastest way to connect OpenClaw to Pneumatic: link your Pneumatic account once in the browser and OpenClaw can call the Pneumatic API through 10 ready-made tools — no custom code or token handling. ### How do I add Pneumatic to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Pneumatic skill from ClawHub, then you click Connect in the dashboard to authorize Pneumatic. OpenClaw calls the tools from the next message — no config files, and the Pneumatic key you paste is stored server-side instead of in your environment. ### How long does it take to connect Pneumatic to OpenClaw? About two minutes. Sign in, click Connect next to Pneumatic in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Pneumatic 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 Pneumatic working from chat. ### OpenClaw installed the Pneumatic skill but can't call the tools The ClawHub skill teaches OpenClaw about Pneumatic, but the calls run through the ClawLink plugin and your connected account. Make sure Pneumatic 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 Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [OpenClaw Moco integration](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp tools](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints