Make collaborator onboarding easier to pick up
Adding a collaborator starts a chain of small tasks. Notis can retrieve the Coassemble user list so onboarding context is available immediately.
Trigger
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.
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
New collaborators are added to code access but their training identity and onboarding status remain unclear.
- Reduces duplicate user checks
- Makes onboarding records easier to find
- Creates a clear handoff point for training follow-up
Setup
Build it in a few focused steps.
- 1Connect GitHub and Coassemble to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Instruct Notis to retrieve Coassemble users relevant to each newly added GitHub collaborator and report possible matches.
- 4Select the new collaborator trigger, choose a run-report channel, and test with one collaborator addition.
Questions about this workflow
Can this create the new learner?
No. The available action retrieves users only; creation is outside this workflow.
Can I include the collaborator's role?
Yes. Mention that Notis should use the GitHub permission or role context when reviewing matches.
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.