--- title: "Chatwork Integration" description: "Automate Chatwork, Japan's leading business chat platform, across messages, chats, members, tasks, and files. Agents post updates, assign chat tasks, and pull the thread context a decision needs." url: https://flowrunner.ai/integrations/chatwork date_modified: 2026-08-07T17:20:23-07:00 --- # Chatwork [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Automate Chatwork, Japan's leading business chat platform, across messages, chats, members, tasks, and files. Agents post updates, assign chat tasks, and pull the thread context a decision needs. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 32 actions · API key · available [Chatwork website](https://chatwork.com/) · [Platform Documentation](https://developer.chatwork.com/) · Capability data verified 2026-08-03 1. A customer replies in a shared project chat and On New Message fires 2. Agent reads the message and the surrounding thread with List Messages 3. Agent classifies the reply as a change request rather than a status question 4. Agent lists the chat's members and current open tasks to see who already owns nearby work 5. Agent posts a summary of the request back into the chat so the customer sees it was received 6. The project lead names the owner and the deadline, and the agent files it with Create Task ## What This Integration Enables Chatwork is Japan's leading business chat platform, and the reason it fits automation well is structural rather than cosmetic. In most chat tools a request is a message: it scrolls, and whether it gets done depends on who read it. In Chatwork a task is a first-class object attached to a chat, assigned to named members with a deadline and a completion state, and it shows up in that person's counters until it is closed. FlowRunner agents can therefore do something in Chatwork they cannot do in a pure messaging tool: turn a conversation into tracked work without leaving the conversation. The connector reaches the full surface around that. Agents post, edit, and read messages, create and update group chats, manage membership, list and create tasks and flip their status, upload and retrieve files, and administer invitation links and contact requests. On New Message gives a flow a way to react to what people are actually saying in a chat, filtered by sender or by phrase so a busy room does not fire on every line. Used together, the agent handles the intake and the record keeping, and the humans in the chat keep the judgment about what matters and who does it. ### Without FlowRunner **Requests live in the thread**: A change asked for in chat is only as durable as the person who happened to read it **Ownership is implied**: Nobody is formally assigned, so the request is either done twice or not at all **Manual task entry**: Someone rereads the thread later and retypes the request as a task ### With FlowRunner **Requests become objects**: Each request lands as a Chatwork task with an assignee, a deadline, and a completion state **Ownership is explicit**: The task appears in one named person's task counter rather than in a shared scroll **Assignment stays human**: The agent prepares the task and a lead decides whose day it belongs on ## Use Case Scenarios ### A customer request in chat becomes a tracked task A client writes into a shared project chat asking for a scope change. On New Message fires, the agent reads the message with the surrounding thread for context, and classifies it as a change request rather than a question. It drafts a task with the request restated in one line, a suggested assignee based on who owns the nearby work, and a proposed deadline, then asks the project lead to confirm before Create Task fires. The request stops being a message and becomes a row in someone's queue. ### Ticket escalations filed as chat tasks with the thread attached When a ticket in [Jira](https://flowrunner.ai/integrations/jira-issues) or [Zendesk](https://flowrunner.ai/integrations/zendesk) is escalated, the agent posts the ticket summary into the relevant Chatwork group chat and creates a matching Chatwork task assigned to the on-call engineer. As the ticket moves, the agent edits the original message with Update Message rather than posting a new one, so the chat carries one current version instead of a trail of stale updates. When the ticket closes, Update Task Status marks the Chatwork task complete. ### Chat history and files archived out of Chatwork A compliance flow walks selected chats on a schedule, pulls messages with List Messages and file metadata with List Files, and writes both into a searchable store. Download URLs from Get File expire quickly, so the agent fetches and stores the file in the same run rather than saving a link that will be dead by the time anyone clicks it. The chat stays the working surface; the archive becomes the record. ## Human-in-Loop Highlight Create Task is not a notification. It assigns a piece of work, with a deadline, to a specific named person, and it lands in the counter that person checks to decide what their day looks like. An agent that files tasks from inbound chat can be right about the work and still wrong about the owner, which is the kind of [automation exception](https://flowrunner.ai/concepts/automation-exceptions) that quietly costs a team more than a missed message would. So the agent does the assembly and stops before the assignment: "Kubo-san asked in the Northwind chat to move the delivery date. I read it as a scope change, not a status question. Suggested owner Tanaka based on the last three tasks in this chat, suggested deadline Friday. File it to Tanaka, reassign, or hold?" The lead answers on the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) channel they already use, and only then does Create Task run. The same discipline applies to Update Chat Members, which replaces a chat's entire membership in one call and silently removes anyone the agent omitted, and to Leave Or Delete Chat, which destroys the chat for everyone. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 32 actions ### Account 4 - **Get My Profile** Returns the full profile of the account the API token belongs to, including account ID, Chatwork ID, organization, department, and contact details. Used to resolve the agent's own identity before it posts or assigns anything. - **Get My Status** Returns unread and task counters for the authenticated account: chats with unread messages, chats containing mentions, total unread and mention counts, and open tasks assigned to it. Used as a cheap check on whether anything needs attention before a fuller read. - **List My Tasks** Lists tasks assigned to the authenticated account across every chat, optionally narrowed to one requester or completion state. Used for backlog digests and overdue sweeps. - **List Contacts** Lists every contact of the authenticated account with account ID, display name, organization, department, and the room ID of the direct chat with them. Used to resolve a person to the direct chat where the agent can reach them. ### Chats 7 - **List Chats** Lists every chat the authenticated account belongs to, including My Chat, direct chats, and group chats. Used to resolve a chat by name before posting. - **Get Chat** Retrieves a single chat's name, description, icon, type, your role in it, and its unread, file, and task counters. Used to confirm the agent has the right room and the right permission level. - **Create Group Chat** Creates a new group chat and returns its room ID. Used to provision a per project or per customer chat as part of an onboarding flow. - **Update Chat** Changes a group chat's name, description, or preset icon. Used to keep a project room's title in step with its status upstream. - **Leave Or Delete Chat** Removes the authenticated account from a group chat, or deletes the chat entirely. Deletion is irreversible and destroys the chat for everyone in it, so it belongs behind an approval rather than behind a rule. - **List Chat Members** Lists every member of a chat with account ID, role, display name, organization, and department. Used to work out who is present before assigning work or posting a mention. - **Update Chat Members** Replaces a chat's entire membership in a single call. Anyone omitted from the call is removed, so the agent should read the current membership first and treat the write as a full replacement, not an addition. ### Messages 7 - **List Messages** Retrieves recent messages from a chat with sender, body, and timestamps. Used to give the agent the thread context behind a single line before it acts. - **Send Message** Posts a message to a chat and returns the new message ID. Used for status updates, escalations, and confirmations back to the people in the room. - **Get Message** Retrieves a single message by ID with its sender, body, and timestamps. Used when a task or ticket records the originating message and the flow needs to go back to it. - **Update Message** Replaces the body of a message the agent previously sent. Used to keep one live status message current instead of stacking updates in the chat. - **Delete Message** Permanently deletes a message the agent previously sent. Used for cleanup, and used carefully, because a message that recorded a decision is part of the record of that decision. - **Mark Messages Read** Marks a chat's messages as read up to a given message. Used to keep the automation account's unread counters honest after a flow has processed a room. - **Mark Messages Unread** Marks a chat as unread from a given message so it reappears in the unread list. Used to hand a room back to human attention deliberately. ### Tasks 4 - **List Chat Tasks** Lists tasks in a chat, optionally filtered by assignee, requester, or completion state. Used for standup digests and for checking whether a request has already been filed. - **Create Task** Adds a task to a chat and assigns it to one or more members, returning one task ID per assignee. This is the action that turns a conversation into someone's work, which is why it belongs behind a human decision about ownership. - **Get Task** Retrieves a single task with its assignee, requester, originating message ID, deadline, and completion state. Used to trace a task back to the message that caused it. - **Update Task Status** Marks a task complete or reopens it. Used to close the Chatwork task when the upstream ticket or record it mirrors is resolved. ### Files 3 - **List Files** Lists files uploaded to a chat, optionally narrowed to a single uploader. Used to inventory what a room holds before archiving it. - **Get File** Retrieves a file's metadata and, when requested, a temporary download URL. The URL expires quickly, so the agent should fetch the content in the same run rather than store the link. - **Upload File** Uploads a file to a chat from a publicly reachable URL and returns the new file ID. Used to deliver a generated report or a signed document into the room where it will be discussed. ### Invitation Links 4 - **Get Invitation Link** Retrieves a chat's invitation link settings. Used to check whether a room is currently open to joiners before an audit or a cleanup. - **Create Invitation Link** Publishes a new invitation link for a chat. Used when a flow provisions an external collaboration room and needs a join path. - **Update Invitation Link** Changes an existing invitation link's code, description, or approval requirement. Used to rotate a link or to add approval to a room that has grown beyond its original audience. - **Delete Invitation Link** Withdraws a chat's invitation link so it can no longer be used to join. Used to close a room at the end of an engagement. ### Contact Requests 3 - **List Contact Requests** Lists pending contact approval requests addressed to the authenticated account, with each requester's details and their message. Used to surface pending requests for a human to decide on. - **Approve Contact Request** Accepts a pending contact approval request and adds the requester to your contacts. Used after a person, not a rule, has decided the requester belongs. - **Reject Contact Request** Declines a pending contact approval request. Used to clear requests that fall outside an agreed policy. ## Triggers 1 triggers ### Event Triggers 1 - **On New Message** Fires for each new message posted in the selected chat. The first run records a baseline and emits nothing, then every unseen message fires once, oldest first, de-duplicated by message ID. The trigger can be restricted to a single sender or to messages containing a given phrase, which is how a busy room becomes a usable trigger rather than a firehose. Used to start intake, escalation, and archival flows from what people actually say. ## Frequently Asked Questions ### What can FlowRunner do with Chatwork? FlowRunner agents can run Get My Profile, Get My Status, and List My Tasks in Chatwork, plus 29 more actions. ### Does connecting Chatwork to FlowRunner require OAuth? No. Chatwork connects to FlowRunner with an API key, no OAuth flow required. ### Can Chatwork trigger a FlowRunner workflow automatically? Yes. Chatwork supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Chatwork?** This integration exposes Chatwork to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/chatwork. Site index: https://flowrunner.ai/llms.txt