Send Messages and Manage Tasks with Chatwork in Jinba Flow

Use the five Chatwork tools to send and read messages, create and list tasks, and update task status in a Jinba Flow workflow.

Use the Chatwork tools when a flow needs to work with a Chatwork room. All five tools require a Chatwork API token in the token configuration and a room_id input. Set up the token before running a flow.

Choose a Chatwork operation

Task	Tool ID	Required input	Result
Send a message	CHATWORK_SEND_MESSAGE	room_id, message	result.message_id
Read messages	CHATWORK_GET_MESSAGES	room_id	result: array of messages
Create a task	CHATWORK_CREATE_TASK	room_id, body, to_ids	result.task_ids: array of task IDs
List tasks	CHATWORK_GET_TASKS	room_id	result: array of tasks
Change a task’s status	CHATWORK_UPDATE_TASK_STATUS	room_id, task_id, status	result.task_id

CHATWORK_GET_MESSAGES accepts optional Boolean force: true fetches up to 100 latest messages; the default false fetches only new messages. CHATWORK_GET_TASKS can filter by account_id, assigned_by_account_id, or status (open or done). CHATWORK_CREATE_TASK accepts optional limit (a Unix timestamp or YYYY/MM/DD date) and limit_type (none, date, or time).

Send a Chatwork message

- id: send_message
  tool: CHATWORK_SEND_MESSAGE
  config:
    - name: token
      value: "{{secrets.CHATWORK_API_TOKEN.api_token}}"
  input:
    - name: room_id
      value: "123456"
    - name: message
      value: "The report is ready."

A successful run returns result.message_id, the ID of the sent message. If the step fails, check that the token is valid, the bot or user can access the room, and the room_id is correct. The input field is message, not body; the configuration field is token, not api_token.

Send a dynamic report to Chatwork

A message can combine results from earlier steps. This keeps the weekly report example from the former advanced guide; replace the step IDs and result fields with outputs from your flow.

- id: send_weekly_report
  tool: CHATWORK_SEND_MESSAGE
  needs: [sales_data, metrics, action_items]
  config:
    - name: token
      value: "{{secrets.CHATWORK_API_TOKEN.api_token}}"
  input:
    - name: room_id
      value: "123456"
    - name: message
      value: |
        Weekly report
        Sales summary: {{ steps.sales_data.result.summary }}
        Key metrics: {{ steps.metrics.result.kpi }}
        Action items: {{ steps.action_items.result.summary }}

Create and complete a Chatwork task

- id: create_task
  tool: CHATWORK_CREATE_TASK
  config:
    - name: token
      value: "{{secrets.CHATWORK_API_TOKEN.api_token}}"
  input:
    - name: room_id
      value: "123456"
    - name: body
      value: "Review the report"
    - name: to_ids
      value: "6454321"

To assign several people, set to_ids to a comma-separated string of account IDs, such as "6454321,7654321".

To complete the task in a later step, use the ID returned by create_task:

- id: complete_task
  tool: CHATWORK_UPDATE_TASK_STATUS
  needs: [create_task]
  config:
    - name: token
      value: "{{secrets.CHATWORK_API_TOKEN.api_token}}"
  input:
    - name: room_id
      value: "123456"
    - name: task_id
      value: "{{steps.create_task.result.task_ids[0]}}"
    - name: status
      value: done

This keeps the task-management workflow from the former advanced page while using the current field names. Check result.task_id to verify which task changed.

Review open tasks

CHATWORK_GET_TASKS can retrieve open tasks for a room, then pass them to a later step for a status report. Use account_id to limit the report to one assignee when needed.

- id: list_open_tasks
  tool: CHATWORK_GET_TASKS
  config:
    - name: token
      value: "{{secrets.CHATWORK_API_TOKEN.api_token}}"
  input:
    - name: room_id
      value: "123456"
    - name: status
      value: open

The result is an array of task records. Each task includes its body, status, and limit_time (a Unix timestamp when a due time is set). Use the returned list to prepare a reminder or report; an empty array means there are no matching tasks.

To monitor deadlines, compare each set limit_time with the current time in a Python step and group open tasks as overdue or upcoming. limit_time is a Unix timestamp, so convert it to a date before displaying it to people.

Review recent messages

Use CHATWORK_GET_MESSAGES to fetch new messages since the last fetch, or set force to true to fetch up to 100 latest messages. The result is a message array with each message’s body, sender account, and send and update timestamps. You can pass this array to a later analysis step to identify topics, questions, and action items.

- id: get_recent_messages
  tool: CHATWORK_GET_MESSAGES
  config:
    - name: token
      value: "{{secrets.CHATWORK_API_TOKEN.api_token}}"
  input:
    - name: room_id
      value: "123456"
    - name: force
      value: true

The result is a message array at steps.get_recent_messages.result. You can analyze it and post a dynamic report to the same room. This example summarizes the latest messages with OPENAI_INVOKE; configure OpenAI access or Jinba credit before running it.

- id: summarize_messages
  tool: OPENAI_INVOKE
  needs: [get_recent_messages]
  input:
    - name: prompt
      value: |
        Summarize these recent Chatwork messages. List key topics, unanswered questions, and action items. Do not invent details.
        {% for message in steps.get_recent_messages.result %}
        - {{ message.account.name }}: {{ message.body }}
        {% endfor %}

- id: send_message_report
  tool: CHATWORK_SEND_MESSAGE
  needs: [summarize_messages]
  config:
    - name: token
      value: "{{secrets.CHATWORK_API_TOKEN.api_token}}"
  input:
    - name: room_id
      value: "123456"
    - name: message
      value: |
        Recent message report
        {{ steps.summarize_messages.result.content }}