Make Jira changes easier to route to the right people
When issue ownership or status changes, Notis can retrieve the room roster and help you prepare a clear follow-up for the team.
Trigger
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.
Action
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.
Why this helps
A Jira change can require coordination, but figuring out who is in the relevant Chatwork room adds another step.
- See the current room roster alongside an issue change
- Prepare a more informed handoff
- Avoid manually switching apps to check membership
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 room members and suggest a concise follow-up based on the Jira update.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue update.
Questions about this workflow
Which Jira changes start the workflow?
Updates to issues in the configured Jira project can start it, including changes to status or assignee. Comment activity does not trigger this event.
Does it send a Chatwork message?
The available action retrieves room members. It can help prepare a follow-up suggestion, but no message-sending action is listed here.
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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.
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.
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.
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.
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.
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.
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.