Keep people and learner records easier to cross-check
A new assignee or issue change can make a different person relevant to training. Ask Notis to retrieve Coassemble users and summarize likely directory matches for a quick human check.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
It takes extra attention to remember whether newly involved people are visible in the learner directory.
- Prompt user visibility checks when issue context changes.
- Reduce repetitive searches through Coassemble users.
- Make potential directory gaps easier to review.
Setup
Build it in a few focused steps.
- 1Connect Linear and Coassemble to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to check user visibility after issue changes.
- 3Write one plain-language instruction asking Notis to retrieve users and summarize likely matches for the people relevant to the updated issue.
- 4Pick the Linear Issue Updated trigger and choose a channel for run reports.
- 5Test with one real issue update involving a relevant person.
Questions about this workflow
Can it add missing users?
No. The available action retrieves users but does not create users or enroll learners.
Will it always identify an exact match?
No. Treat the summary as a lookup aid for human review, especially if available names or context are incomplete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Coassemble. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
Get Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.