Chatwork

Communication

Chatwork for AI agents. Managed auth, ready-made tools.

Read and post messages in Chatwork rooms and create and track tasks on behalf of each of your users.

About Chatwork

With the Chatwork connector, your agent works in each user’s own Chatwork account. It can list their rooms, read and post messages, see their open tasks and assign new ones, using only the tools your project allows.

Chatwork is a business chat tool with group chats, tasks and file sharing.

Tools

What your agent can do in Chatwork.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Chatwork connection.

  • List rooms

    Read
    chatwork_list_rooms

    List the chat rooms the user belongs to.

  • Read a room

    Read
    chatwork_get_messages

    Read recent messages in a room.

  • Post a message

    Write
    chatwork_post_message

    Post a message in a room.

  • List my tasks

    Read
    chatwork_list_tasks

    List the tasks assigned to the user.

  • Create a task

    Write
    chatwork_create_task

    Assign a task in a room with an optional due date.

  • List contacts

    Read
    chatwork_list_contacts

    List the user's Chatwork contacts.

Control

Limits you can set.

You decide what your agent may do in Chatwork, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read rooms and tasks, and switch off chatwork_post_message so it can never post a message.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example rooms and messages but not tasks. A call outside them is refused.

Get started

Connect Chatwork
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Chatwork

    Each end user authorizes their own Chatwork account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Chatwork account, once.
    const connection = await agent200
      .user("user_123")
      .connect("chatwork");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Chatwork tools

    Name the user, the model and the tools. The model decides which Chatwork tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "What did the sales room discuss today",
        tools: ["chatwork"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Chatwork's own sign-in page. You never see or store their Chatwork password.

  • What access is requested

    The scopes the connection needs, such as reading rooms, writing messages or managing tasks, listed on Chatwork's authorization screen. Users can remove the app later from their Chatwork account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Chatwork connector and how to use it.

Agent brief
Connector: Chatwork, through Agent200. In code: "chatwork".
What it does: Read and post messages in Chatwork rooms and create and track tasks on behalf of each of your users.
Page: https://www.agent200.com/connectors/chatwork/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Chatwork's own page, through the authorization link Agent200 returns. Never ask a user for a Chatwork password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: chatwork_list_rooms, chatwork_get_messages, chatwork_list_tasks, chatwork_list_contacts. Write tools: chatwork_post_message, chatwork_create_task. Name "chatwork" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/chatwork/framework/claude/
   https://www.agent200.com/connectors/chatwork/framework/chatgpt/
   https://www.agent200.com/connectors/chatwork/framework/claude-code/
   https://www.agent200.com/connectors/chatwork/framework/muse/
   https://www.agent200.com/connectors/chatwork/framework/grok-bot/
   https://www.agent200.com/connectors/chatwork/framework/openai-dots/
   https://www.agent200.com/connectors/chatwork/framework/claude-duet/
   https://www.agent200.com/connectors/chatwork/framework/hermes-agent/
   https://www.agent200.com/connectors/chatwork/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/chatwork.md

Guides

Use Chatwork with the AI you build on.

Step-by-step setup for Chatwork with a specific model, assistant or agent framework.

FAQ

Chatwork and Agent200, answered.

Who handles the Chatwork OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Chatwork.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Chatwork connection, never another user's. It cannot reach anything the user or Chatwork has not authorized.

Can I limit what my agent can do in Chatwork?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Slack

    Slack

    Search conversations and post messages in the workspaces your users connect.

    Managed OAuth Communication
  • Microsoft Teams

    Microsoft Teams

    Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.

    Managed OAuth Communication
  • Discord

    Discord

    Read channels, post messages and start threads in the Discord servers your users connect.

    Managed OAuth Communication
  • Zoom

    Zoom

    Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

    Managed OAuth Communication
200 OK

Start with Chatwork.
Your agent does the rest.

Your users connect their own Chatwork accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)