Get the next step from a failed check
Individual check failures become understandable, prioritized debugging prompts instead of interruptions with no direction.
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
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 single failed check can derail focus because its label rarely explains the real next step.
- Translate failure signals into action
- Reduce debugging guesswork
- Protect focused work time
Setup
Build it in a few focused steps.
- 1Connect GitHub and Ai ml api to Notis once through the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Use this instruction: When a GitHub check run reaches a failure, error, or action-required conclusion, ask Ai ml api to explain the signal and recommend one focused next debugging step, then send me the result.
- 4Select the check run status trigger and choose where run reports should arrive.
- 5Test it with one failed check run.
Questions about this workflow
Can it focus on action-required checks?
Yes. Include action-required in the conditions described in the instruction.
Why use this instead of the check suite workflow?
This workflow focuses on one individual check, making the guidance more targeted.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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.
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.
Connect any two apps with Notis in the middle.
GitHub and Ai ml api, 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 Ai ml api.