# How to connect Kanbanize to OpenClaw (paste one key, 24 tools) > Connect Kanbanize to OpenClaw with ClawLink: paste your Kanbanize key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/kanbanize The usual route to Kanbanize 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 Kanbanize setup: install one ClawHub skill, connect Kanbanize in the browser, and OpenClaw can call real Kanbanize 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 Kanbanize. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Kanbanize** — 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 kanbanize # connect Kanbanize (browser OAuth) npx -y @useclawlink/cli actions kanbanize # list available actions npx -y @useclawlink/cli run kanbanize --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 Kanbanize in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Kanbanize API key once. Verify the connection by asking OpenClaw: > Use Kanbanize to check board milestone 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 Kanbanize is connected in the dashboard, that agent calls the same 24 Kanbanize 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). ## Kanbanize MCP for OpenClaw Looking for a Kanbanize MCP server for OpenClaw? ClawLink connects Kanbanize to OpenClaw and exposes 24 Kanbanize 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 Kanbanize integration](https://claw-link.dev/hermes/kanbanize) works the same way. ## What the OpenClaw Kanbanize integration can do 24 Kanbanize tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 24. ### 20 of 24 Kanbanize tools for OpenClaw | Tool | What it does | |---|---| | **Check board milestone** `kanbanize_check_board_milestone` | Check if a milestone is available on the specified board | | **Check user is card watcher** `kanbanize_check_user_is_card_watcher` | Check if a user is a watcher of a specific card | | **Get board block reasons** `kanbanize_get_board_block_reasons` | Get a list of block reasons available on a board | | **Get board card templates** `kanbanize_get_board_card_templates` | Retrieve a list of card templates available on a Kanbanize board | | **Get child cards** `kanbanize_get_child_cards` | Retrieve a list of child cards for a specified parent card | | **Get column** `kanbanize_get_column` | Get the details of a specific column from a Kanbanize board | | **Get columns** `kanbanize_get_columns` | Get a list of columns for a specific board in Kanbanize | | **Get custom fields** `kanbanize_get_custom_fields` | Retrieve a list of custom fields from Kanbanize with optional filtering | | **Get stickers** `kanbanize_get_stickers` | Retrieve a list of stickers with optional filtering by sticker IDs, label, availability, and | | **Get user** `kanbanize_get_user` | Get the details of a specified user in Kanbanize | | **Get workflow cycle time columns** `kanbanize_get_workflow_cycle_time_columns` | Retrieve workflow's cycle time columns from a Kanbanize board | | **Get workspace data fields** `kanbanize_get_workspace_data_fields` | Retrieve a list of data fields available on a workspace | | **Add card comment** `kanbanize_add_card_comment` | Add a comment to a Kanbanize card | | **Set card block reason** `kanbanize_set_card_block_reason` | Block a Kanbanize card by setting a block reason | | **Update board sticker** `kanbanize_update_board_sticker` | Update the properties of a sticker for the specified board | | **Update lane default setting** `kanbanize_update_lane_default_setting` | Update the default value of a specific lane setting in Kanbanize | | **Update tag** `kanbanize_update_tag` | Update the specified tag in Kanbanize | | **Remove board block reason** `kanbanize_remove_board_block_reason` | Make a block reason unavailable on a board | | **Remove child card** `kanbanize_remove_child_card` | Remove the link between a parent card and a child card | | **Update data field workspaces** `kanbanize_update_data_field_workspaces` | Add, update, or remove a data field on one or more workspaces via batch operations | ## Example prompts **Check Board Milestone** > Use Kanbanize to check board milestone and walk me through the result in plain English. **Check User Is Card Watcher** > Use Kanbanize to check user is card watcher and walk me through the result in plain English. **Get Board Block Reasons** > Pull the relevant data from Kanbanize, summarize it in plain English, and point out anything that needs attention. **Get Board Card Templates** > Pull the relevant data from Kanbanize, 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 Kanbanize working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Kanbanize API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Kanbanize 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 Kanbanize. | 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 Kanbanize actions to the runtime in a format your agent can reliably use. | 24 tools for Kanbanize are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Kanbanize 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 Kanbanize in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Kanbanize 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 Kanbanize skill but can't call the tools The ClawHub skill teaches OpenClaw about Kanbanize, but the calls run through the ClawLink plugin and your connected account. Make sure Kanbanize 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 Kanbanize 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 Kanbanize tools Kanbanize 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 Kanbanize 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. ### Kanbanize 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 Kanbanize has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Kanbanize integration? Yes. ClawLink is the fastest way to connect OpenClaw to Kanbanize: link your Kanbanize account once in the browser and OpenClaw can call the Kanbanize API through 24 ready-made tools — no custom code or token handling. ### How do I add Kanbanize to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Kanbanize skill from ClawHub, then you click Connect in the dashboard to authorize Kanbanize. OpenClaw calls the tools from the next message — no config files, and the Kanbanize key you paste is stored server-side instead of in your environment. ### How long does it take to connect Kanbanize to OpenClaw? About two minutes. Sign in, click Connect next to Kanbanize in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Kanbanize 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 Kanbanize working from chat. ### OpenClaw installed the Kanbanize skill but can't call the tools The ClawHub skill teaches OpenClaw about Kanbanize, but the calls run through the ClawLink plugin and your connected account. Make sure Kanbanize 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 - [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