Turn code review moments into training follow-up
A submitted review is a natural pause point. Have Notis retrieve Coassemble progress so the next enablement action is easier to spot.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
Action
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.
Why this helps
Important learner follow-ups get postponed because review activity and training records live in separate systems.
- Creates a predictable review-to-follow-up rhythm
- Makes progress data available at the moment it matters
- Lowers the cost of remembering who needs support
Setup
Build it in a few focused steps.
- 1Connect GitHub and Coassemble to Notis once through the portal.
- 2Create the automation in the portal or describe it to Notis conversationally.
- 3In one plain-language instruction, ask Notis to fetch the relevant Coassemble tracking details when a pull request review is submitted.
- 4Choose the review-submitted trigger, select a run-report channel, and test with a real review.
Questions about this workflow
Can this support different review outcomes?
Yes. Your plain-language instruction can tell Notis how to respond to submitted review events and use the returned tracking data.
Do I need to map review fields manually?
No. Notis interprets the instruction and trigger context without a field-mapping screen.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Coassemble. A trigger fires from one place; an action lands in another.
GitHub triggers
Coassemble actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Get Clients
Tool to retrieve a paginated list of clients. use when you need to browse or process organisation records sequentially.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Coassemble. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Coassemble.