How to connect Carbone to OpenClaw
Connect Carbone to OpenClaw with ClawLink: paste your Carbone key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine.
CarboneAPI KEYMCPCarbone is a fast and simple report generator that converts JSON data into various document formats such as PDF, DOCX, XLSX, ODT, and more, using templates.. Once connected, OpenClaw can read and act on Carbone from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Carbone 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 Carbone setup: install one ClawHub skill, connect Carbone in the browser, and OpenClaw can call real Carbone 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 Carbone.
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 Carbone
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Carbone?"
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 Carbone in the ClawLink dashboard — paste your Carbone API key once.
Verify the connection by asking OpenClaw:
Use Carbone to download template 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Carbone is connected in the dashboard, that agent calls the same 11 Carbone tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Carbone MCP for OpenClaw
Looking for a Carbone MCP server for OpenClaw? ClawLink connects Carbone to OpenClaw and exposes 11 Carbone tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Carbone integration works the same way.
What the OpenClaw Carbone integration can do
11 Carbone tools are ready for OpenClaw once the account is connected. The 10 below are the ones people reach for most; your agent can call all 11.
10 of 11 Carbone tools for OpenClaw
| Tool | What it does |
|---|---|
Download template carbone_download_template | Download a template from Carbone by template ID |
Get status carbone_get_status | Retrieve the current status and health of the Carbone server |
List template categories carbone_list_template_categories | Retrieve a list of all categories used in templates |
List template tags carbone_list_template_tags | List all tags currently used in templates |
List templates carbone_list_templates | Retrieve a list of templates from Carbone storage with filtering, search, and cursor-based |
Render template direct carbone_render_template_direct | Generate a document by uploading a base64-encoded template and data in a single API call |
Set API version carbone_set_api_version | Set the Carbone API version to be used for subsequent requests |
Generate report carbone_generate_report | Generate a Carbone report from a template and JSON data |
Update template carbone_update_template | Update metadata and attributes of an existing Carbone template |
Upload template carbone_upload_template | Upload a template file to the Carbone server to obtain a template ID for document generation |
Try it: find the Carbone tool you need
Browse the 10 Carbone tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Carbone to download template and walk me through the result in plain English.
Pull the relevant data from Carbone, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Carbone, 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 Carbone working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Carbone API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Carbone 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 Carbone. | 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 Carbone actions to the runtime in a format your agent can reliably use. | 11 tools for Carbone are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Carbone 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 Carbone in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Carbone 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 Carbone skill but can't call the tools
The ClawHub skill teaches OpenClaw about Carbone, but the calls run through the ClawLink plugin and your connected account. Make sure Carbone 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 Carbone 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 Carbone tools
Carbone 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 Carbone 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.
Carbone 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 Carbone 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 Carbone integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Carbone: link your Carbone account once in the browser and OpenClaw can call the Carbone API through 11 ready-made tools — no custom code or token handling.
How do I add Carbone to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Carbone skill from ClawHub, then you click Connect in the dashboard to authorize Carbone. OpenClaw calls the tools from the next message — no config files, and the Carbone key you paste is stored server-side instead of in your environment.
How long does it take to connect Carbone to OpenClaw?
About two minutes. Sign in, click Connect next to Carbone in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Carbone 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 Carbone working from chat.
OpenClaw installed the Carbone skill but can't call the tools
The ClawHub skill teaches OpenClaw about Carbone, but the calls run through the ClawLink plugin and your connected account. Make sure Carbone 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
GitHub tools
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
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.