Skip to content
Notis

Find the right Chatwork contacts for a Jira handoff

When a handoff needs a fresh start, trigger Notis and get contact context to help identify who should be involved.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Get Chatwork Contacts

This tool retrieves a list of all contacts from chatwork. it is a fundamental tool that fetches all contact information such as account id, room id, name, chatwork id, organization details, department, and avatar image url, without needing additional parameters beyond authentication.

Why this helps

Finding the right people for a Jira handoff can mean searching contacts and rebuilding context from scratch.

  • Retrieve available Chatwork contact details on demand
  • Prepare a people-aware handoff summary
  • Avoid a manual contact search

Setup

Build it in a few focused steps.

  • 1Connect Jira and Chatwork once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, ask Notis to retrieve Chatwork contacts and prepare a concise handoff summary from the supplied Jira context.
  • 4Pick the Notis webhook trigger and choose where run reports should go.
  • 5Test with one real example.

Questions about this workflow

What starts this workflow?

An HTTP request to the configured Notis webhook starts it.

Does the webhook provide Jira details automatically?

Only include Jira context in the request if it is available to your webhook caller; the contact action itself retrieves Chatwork contacts.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Chatwork. A trigger fires from one place; an action lands in another.

Jira triggers

Chatwork actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Delete Message

This tool allows you to delete a specific message from a chatwork room by calling the delete endpoint at https://api.chatwork.com/v2/rooms/{room id}/messages/{message id}. it requires authentication using a chatwork api token provided in the x-chatworktoken header, and the necessary permissions to delete messages in the specified room.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Chatwork Contacts

This tool retrieves a list of all contacts from chatwork. it is a fundamental tool that fetches all contact information such as account id, room id, name, chatwork id, organization details, department, and avatar image url, without needing additional parameters beyond authentication.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Get Chatwork File

This tool retrieves information about a specific file in a chat room. the api endpoint get /v2/rooms/{room id}/files/{file id} provides file details such as file id, account id, message id, filename, filesize, upload time, and download url, which are useful for retrieving file metadata, verifying file existence, and managing file sharing within chatwork.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Get My Chatwork Status

This tool retrieves the current status of the authenticated user, including unread message counts and task status. it provides a quick overview of unread messages, mentions, and tasks, making it valuable for monitoring chatwork activity and building automation workflows.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Get Room Members

This tool retrieves a list of all members in a specified chatwork room using the endpoint get /rooms/{room id}/members. it provides essential details like account id, role, name, chatwork id, organization id, and organization name, complementing the existing suite of room management tools.

ActionInstant

Get Room Messages

This tool retrieves messages from a specific chatwork room using the get https://api.chatwork.com/v2/rooms/{room id}/messages endpoint. it requires a room id parameter and an optional force flag to refresh the cache by retrieving the 100 newest messages.

ActionInstant

Get Chatwork Rooms

This tool retrieves a list of all chat rooms associated with the authenticated chatwork account. it includes group chats, direct chats, and personal chats, and does not require any additional parameters beyond authentication.

ActionInstant

Upload File to Chatwork Room

This tool allows users to upload files to a specific chatwork room. it enables file sharing functionality within the chatwork platform by providing an endpoint to upload files (along with an optional message) to a given room.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Chatwork, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Chatwork.