Keep ChMeetings meeting details current as Jira changes
When work changes in Jira, Notis can update the related ChMeetings meeting so the conversation starts with current context.
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
ChMeetings: Update Meeting
Tool to update meeting details. Use when modifying an existing meeting; call after retrieving meeting ID.
Why this helps
Meeting details go stale when an issue's status, assignee, or other fields change after planning.
- Reflect changed issue context in a related meeting.
- Reduce last-minute manual meeting edits.
- Keep project discussions anchored to current work.
Setup
Build it in a few focused steps.
- 1Connect Jira and ChMeetings once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis how to identify the related meeting and which available issue changes should update its details.
- 4Pick Jira's Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue update and review the meeting changes.
Questions about this workflow
Does this trigger on Jira comments?
No. The Updated Issue event covers changes to an issue's fields and does not fire on comment activity.
How will Notis find the right meeting?
The action updates a meeting and requires the relevant meeting identity. Your instruction needs to explain how Notis can identify the related meeting from available context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Chmeetings. A trigger fires from one place; an action lands in another.
Jira triggers
Chmeetings actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Invite Meeting Attendee
Tool to invite a new attendee to a specified meeting. Use when you need to add attendees before the meeting begins.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Attendee Details
Tool to retrieve details for a specific attendee. Use when you have an attendee_id and need the attendee's full profile.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
New Project
Triggered when a new project is added in Jira
ChMeetings: Create Organization
Tool to create a new organization.
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.
ChMeetings: Create Reminder
Tool to create/schedule a reminder for a meeting in ChMeetings.
Delete Meeting Attendee
Tool to remove an attendee from a meeting. Use after confirming attendee details.
List Meeting Attendees
Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting.
ChMeetings: Delete Meeting
Tool to delete an existing meeting. Use when you have confirmed the meeting ID to permanently remove the meeting.
Connect any two apps with Notis in the middle.
Jira and Chmeetings, 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 Chmeetings.