How to connect Chatwork to OpenClaw
Connect Chatwork to OpenClaw with ClawLink: paste your Chatwork key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine.
ChatworkAPI KEYMCPChatwork is a team communication platform featuring group chats, file sharing, and task management, aiming to enhance collaboration and productivity for businesses.. Once connected, OpenClaw can read and act on Chatwork from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Chatwork 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 Chatwork setup: install one ClawHub skill, connect Chatwork in the browser, and OpenClaw can call real Chatwork 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 Chatwork.
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 Chatwork
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Chatwork?"
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 Chatwork in the ClawLink dashboard — paste your Chatwork API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Chatwork, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Chatwork is connected in the dashboard, that agent calls the same 30 Chatwork tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Chatwork MCP for OpenClaw
Looking for a Chatwork MCP server for OpenClaw? ClawLink connects Chatwork to OpenClaw and exposes 30 Chatwork tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Chatwork integration works the same way.
What the OpenClaw Chatwork integration can do
30 Chatwork tools are ready for OpenClaw once the account is connected. The 27 below are the ones people reach for most; your agent can call all 30.
27 of 30 Chatwork tools for OpenClaw
| Tool | What it does |
|---|---|
Get chatwork contacts chatwork_get_chatwork_contacts | Retrieves a list of all contacts from Chatwork |
Get file2 chatwork_get_file2 | Get information about a specific file in a chat room |
Get incoming requests chatwork_get_incoming_requests | Retrieve pending contact approval requests received by the authenticated user |
Get me chatwork_get_me | Retrieve the authenticated user's profile information including account details, organization |
Get message chatwork_get_message | Retrieve information about a specific message in a Chatwork room |
Get my status chatwork_get_my_status | Retrieves the current status of the authenticated user, including unread message counts and |
Get my tasks chatwork_get_my_tasks | Retrieve the authenticated user's task list from Chatwork (up to 100 items) |
Get room chatwork_get_room | Retrieves detailed information about a specific Chatwork room using the API endpoint GET |
Get room files chatwork_get_room_files | Get list of files in a chat room (up to 100 files) |
Get room link chatwork_get_room_link | Retrieves the invitation link for a specified Chatwork room using the API endpoint GET |
Get room members chatwork_get_room_members | Retrieves a complete list of all members in a specified Chatwork room using the API endpoint |
Get room messages2 chatwork_get_room_messages2 | Retrieve messages from a Chatwork room (up to 100 messages) |
Get room tasks chatwork_get_room_tasks | Retrieves a list of tasks from a Chatwork room |
Get rooms2 chatwork_get_rooms2 | Retrieve a list of all chat rooms the authenticated user belongs to |
Get task chatwork_get_task | Retrieves detailed information about a specific task in a Chatwork room using the API endpoint |
Create room chatwork_create_room | Create a new group chat room in Chatwork |
Create room link chatwork_create_room_link | Create an invitation link for a Chatwork room |
Create task chatwork_create_task | Create a new task in a Chatwork room |
Mark messages read chatwork_mark_messages_read | Mark messages as read in a Chatwork room |
Mark messages unread chatwork_mark_messages_unread | Mark messages as unread in a Chatwork room |
Post message chatwork_post_message | Post a new message to a Chatwork room |
Update message chatwork_update_message | Update an existing message in a Chatwork room |
Update room chatwork_update_room | Update chat room information (name, icon, description) |
Update room link chatwork_update_room_link | Update the invitation link settings for a Chatwork room |
Update room members chatwork_update_room_members | Updates the complete member list of a Chatwork room with bulk assignment of member roles |
Update task status chatwork_update_task_status | Update the completion status of a task in a Chatwork room |
Upload file chatwork_upload_file | Allows users to upload files to a specific Chatwork room |
Try it: find the Chatwork tool you need
Browse the 27 Chatwork tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Chatwork, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chatwork, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chatwork, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chatwork, 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 Chatwork working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Chatwork API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Chatwork 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 Chatwork. | 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 Chatwork actions to the runtime in a format your agent can reliably use. | 30 tools for Chatwork are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Chatwork 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 Chatwork in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Chatwork 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 Chatwork skill but can't call the tools
The ClawHub skill teaches OpenClaw about Chatwork, but the calls run through the ClawLink plugin and your connected account. Make sure Chatwork 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 Chatwork 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 Chatwork tools
Chatwork 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 Chatwork 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.
Chatwork 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 Chatwork 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 Chatwork integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Chatwork: link your Chatwork account once in the browser and OpenClaw can call the Chatwork API through 30 ready-made tools — no custom code or token handling.
How do I add Chatwork to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Chatwork skill from ClawHub, then you click Connect in the dashboard to authorize Chatwork. OpenClaw calls the tools from the next message — no config files, and the Chatwork key you paste is stored server-side instead of in your environment.
How long does it take to connect Chatwork to OpenClaw?
About two minutes. Sign in, click Connect next to Chatwork in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Chatwork 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 Chatwork working from chat.
OpenClaw installed the Chatwork skill but can't call the tools
The ClawHub skill teaches OpenClaw about Chatwork, but the calls run through the ClawLink plugin and your connected account. Make sure Chatwork 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.
