Find the right Coassemble learners after Jira changes
A changed Jira issue may affect who needs training follow-up. Ask Notis to retrieve Coassemble users relevant to the issue and surface the records worth checking.
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 Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
Why this helps
Keeping learner details aligned with changing Jira work can mean repeated searches and missed follow-ups.
- Retrieve Coassemble users when an existing issue changes.
- Reduce repeated app switching to check learner records.
- Receive a concise lookup report in a selected channel.
Setup
Build it in a few focused steps.
- 1Connect Jira and Coassemble once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe which learner records to look up when an issue changes.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real updated issue and review the results.
Questions about this workflow
Does the trigger run for Jira comments?
No. Updated Issue does not fire for comment activity. It fires when an issue field changes in the configured project.
Can this enroll a learner in a course?
No. The available Coassemble action retrieves user records. It does not enroll learners.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Coassemble. A trigger fires from one place; an action lands in another.
Jira triggers
Coassemble actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Clients
Tool to retrieve a paginated list of clients. use when you need to browse or process organisation records sequentially.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Courses
Tool to retrieve all courses with optional filters and pagination. use when you need to list courses after setting identifier and client identifier, and control page size and number.
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 Trackings
Tool to retrieve tracking objects with filters. use when you need to fetch learner progress data filtered by course id, date range, identifier, or completion status.
New Project
Triggered when a new project is added in Jira
Get Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
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.
Connect any two apps with Notis in the middle.
Jira and Coassemble, 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 Coassemble.