Make CI failures easier to understand
When checks fail, get the likely cause and next move in plain language instead of another wall of logs.
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
Text Chat Completion
Tool to generate text completions or chat responses using a specified llm model. use after assembling the conversation history to produce the next response.
Why this helps
A failed check suite can create a high-friction debugging session before you even know where to look.
- Start debugging with a hypothesis
- Avoid scanning irrelevant logs
- Keep failed builds from stalling progress
Setup
Build it in a few focused steps.
- 1Connect GitHub and Ai ml api to Notis once through the portal.
- 2Create a new automation in the portal or ask Notis to set it up.
- 3Use this instruction: When a GitHub check suite changes to a failed or error conclusion, ask Ai ml api to explain the likely cause, affected area, and next debugging steps from the available context, then send me the result.
- 4Choose the check suite status trigger and select a run-report channel.
- 5Test it with one failed check suite.
Questions about this workflow
Does this fix the failure automatically?
No. It provides a focused explanation and recommended next steps so you can decide what to do.
Can it run only for failures?
Yes. State the failed or error condition in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Ai ml api. A trigger fires from one place; an action lands in another.
GitHub triggers
Ai ml api 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.
Moderation Completion
Tool to classify input text or image for safety using a moderation model. use after receiving user-generated content to filter out unsafe material.
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.
Text Chat Completion
Tool to generate text completions or chat responses using a specified llm model. use after assembling the conversation history to produce the next response.
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 Ai ml api. 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 Ai ml api.