Make workflow-job outcomes easier to act on
A workflow job can point to a technical issue or a process gap. Notis fetches the relevant training context so the next action is clearer.
Trigger
Workflow Job State Changed
Triggers when the status, conclusion, timestamps, runner assignment, or step details of a specific GitHub Actions workflow job change between polls. The payload includes the full current job state, a list of which fields changed, and the previous status/conclusion values for easy comparison.
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
Job-level failures create scattered follow-up tasks that are difficult to prioritize and remember.
- Adds context to job-level outcomes
- Helps prioritize coaching after repeated issues
- Consolidates a lookup founders often postpone
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.
- 3Tell Notis to retrieve Coassemble tracking data when a monitored workflow job changes state and summarize any relevant follow-up.
- 4Select the workflow job state trigger, choose a reporting channel, and test with one job change.
Questions about this workflow
Can it use step details?
Yes. The event includes step details, and your prompt can ask Notis to use them when interpreting the result.
Can I limit reporting to failures?
Yes. Include that preference in the plain-language instruction.
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
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 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 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.
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 Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
Connect any two apps with Notis in the middle.
GitHub 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.