Analyze failed check suites automatically
See the bigger picture when several checks fail together.
Trigger
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.
Action
/api/x402/research
AI-powered Token Deep Research API
Why this helps
A suite failure can represent one root cause or many noisy symptoms, making triage hard to prioritize.
- Distinguish systemic failures from isolated failures.
- Prioritize investigation across multiple checks.
- Create a calmer first response to broken pipelines.
Setup
Build it in a few focused steps.
- 1Connect GitHub and www.capminal.ai to Notis once through the portal.
- 2Create the automation in Automations or ask Notis to set it up.
- 3Use this instruction: Research each GitHub check suite that concludes with failure and explain the most likely shared causes, affected areas, and recommended investigation order.
- 4Choose the check suite status or conclusion trigger and a run-report channel.
- 5Test with one failed suite.
Questions about this workflow
How is this different from a failed check workflow?
It researches the suite-level picture, which is useful when several checks change together.
Can it cover a specific ref?
Yes. The GitHub trigger can monitor the relevant branch, tag, or commit reference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to www.capminal.ai. A trigger fires from one place; an action lands in another.
GitHub triggers
www.capminal.ai 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.
/api/x402/research
AI-powered Token Deep Research API
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.
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.
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 www.capminal.ai. Any 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 www.capminal.ai.