Handle failed checks with the conversation already captured
A failed check can derail a focused day. Pull up the Recallai discussion that may already explain the likely cause and next move.
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
List chat messages
Get list of chat messages read by the bot in the meeting(excluding messages sent by the bot itself).
Why this helps
Build failures trigger urgent context-switching and repeated debugging questions.
- Speeds up failure triage
- Reduces repeated debugging
- Protects deep work time
Setup
Build it in a few focused steps.
- 1Connect GitHub and Recallai to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to retrieve Recallai chat messages when a monitored GitHub check run changes status or concludes unsuccessfully.
- 3Select the Check Run Status / Conclusion Changed trigger and choose the run-report channel.
- 4Test with one monitored check run transition.
Questions about this workflow
Can it focus on failures?
Yes. State in the plain-language instruction that the useful outcome is needed for failed or blocked checks.
Does it fix the check?
No. It retrieves prior conversation context to support faster diagnosis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Recallai. A trigger fires from one place; an action lands in another.
GitHub triggers
Recallai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create bot
Create a new bot.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete bot
Delete a bot by id.
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.
List bots
List all bots
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.
List chat messages
Get list of chat messages read by the bot in the meeting(excluding messages sent by the bot itself).
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Remove bot from call
Removes the bot from the meeting. this is irreversable.
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.
Retrieve bot
Get a bot instance.
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.
Start recording
Instructs the bot to start recording the meeting. this will restart the current recording if one is already in progress.
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.
Stop recording
Instructs the bot to end the current recording.
Connect any two apps with Notis in the middle.
GitHub and Recallai, 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 Recallai.