Chatwork MCP integration for AI agents.
Connect AI agents to Chatwork through 15 structured actions, including get contacts, create task, and delete message. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 15
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Chatwork integration exposes
The Chatwork Agent App exposes 15 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent list chatwork contacts visible to the authenticated account, create a task in a chatwork room, and delete one message in a chatwork room. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Chatwork account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Chatwork capabilities.
Showing 12 of 15 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactsREADList Chatwork contacts visible to the authenticated account.
create_taskWRITECreate a task in a Chatwork room.
INPUTS: roomId / body / assigneeAccountIds / limitTime / limitType
delete_messageHIGH IMPACTDelete one message in a Chatwork room.
INPUTS: roomId / messageId
get_meREADGet the authenticated Chatwork profile.
get_messageREADGet one message from a Chatwork room.
INPUTS: roomId / messageId
get_roomREADGet metadata for one Chatwork room.
INPUTS: roomId
get_taskREADGet one task from a Chatwork room.
INPUTS: roomId / taskId
list_my_tasksREADList Chatwork tasks assigned to the authenticated account.
INPUTS: assignedByAccountId / status
list_room_membersREADList all members in one Chatwork room.
INPUTS: roomId
list_room_messagesREADList messages in one Chatwork room.
INPUTS: roomId / force
list_room_tasksREADList tasks in one Chatwork room.
INPUTS: roomId / accountId / assignedByAccountId / status
list_roomsREADList Chatwork rooms visible to the authenticated account.
INPUT CONTRACTS
Know what the action needs before it runs.
create_task
roomIdREQUIRED- The Chatwork room ID.
bodyREQUIRED- The task body.
assigneeAccountIdsREQUIRED- The assignee Chatwork account IDs.
limitTimeOPTIONAL- The Unix timestamp deadline.
limitTypeOPTIONAL- The deadline type.
delete_message
roomIdREQUIRED- The Chatwork room ID.
messageIdREQUIRED- The Chatwork message ID.
get_message
roomIdREQUIRED- The Chatwork room ID.
messageIdREQUIRED- The Chatwork message ID.
get_room
roomIdREQUIRED- The Chatwork room ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contacts
List Chatwork contacts visible to the authenticated account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_contactsControl Create Task
Create a task in a Chatwork room. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_taskVerify with Get Me
Get the authenticated Chatwork profile. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_meSAFETY BOUNDARY
Operate Chatwork with explicit limits
- Authorize Chatwork with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_message` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Chatwork rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Chatwork task completed successfully.
CONNECTION MODEL
API key
Chatwork API token sent with the X-ChatWorkToken header. Generate it from the Chatwork API settings page.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 11
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Chatwork.