Surface the right runbook for a changed GitHub check
Move from a failed or stalled check to the relevant operating context without remembering where the team stored it.
Trigger
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.
Action
Data API Get Objects
Tool to retrieve a list of objects for a specified data type. use when you need to list items with optional filters, sorting, and pagination.
Why this helps
A failing check creates immediate pressure, while the runbook or component owner needed to respond is hidden in a separate system.
- Shortens the path from failure signal to response context
- Reduces reliance on remembering runbook locations
Setup
Build it in a few focused steps.
- 1Connect GitHub and Project bubble to Notis once.
- 2Create an automation with a plain-language instruction to list the relevant runbook or component objects when the monitored check changes.
- 3Choose Check Run Status / Conclusion Changed as the trigger, choose a reporting channel, and test with one check transition.
Questions about this workflow
Can the automation report only failed conclusions?
Yes. State the conclusions that matter in your plain-language instruction and configure the GitHub trigger for the check you want to monitor.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Project bubble. A trigger fires from one place; an action lands in another.
GitHub triggers
Project bubble 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.
Data API Get Data Type Fields
Tool to get the fields of a specific data type. use after discovering a data type to inspect its fields.
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.
Data API Get Objects
Tool to retrieve a list of objects for a specified data type. use when you need to list items with optional filters, sorting, and pagination.
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 Record By ID
Tool to retrieve a specific record by id from the bubble data api. use after confirming the data type and record id. example: request type='teams', id='a1b2c3d4'.
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.
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 Project bubble. 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 Project bubble.