Bring failed GitHub check suites to the team
Make suite-level CI failures visible without asking everyone to watch GitHub.
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
Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
Why this helps
A suite failure can affect a whole ref, yet the right people may not see it until later.
- Alert on suite-level failure conclusions
- Include the associated ref for context
- Help the team coordinate follow-up
Setup
Build it in a few focused steps.
- 1Connect GitHub and Dailybot once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to post a short Dailybot alert when the check suite conclusion is failure, including the ref and available details.
- 4Pick the Check Suite Status / Conclusion Changed trigger and choose where run reports should go.
- 5Test with one real failed check suite.
Questions about this workflow
What refs can this watch?
The trigger monitors check suites associated with a git reference, such as a branch, tag, or commit SHA.
Does every suite status change send a message?
The event observes status or conclusion changes. Ask Notis to send the alert only when a suite's conclusion is failure.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Dailybot. A trigger fires from one place; an action lands in another.
GitHub triggers
Dailybot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find User by UUID
This tool allows you to find and retrieve information about a specific user in dailybot. it uses the provided user uuid to lookup the user and returns detailed information including the user's uuid, full name, image, username, occupation, birth date, chat platform data, and organization details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Find Workflow by Name
This tool allows users to find a specific workflow within dailybot by providing the workflow name. it returns detailed information including the workflow id, workflow name, workflow status, workflow type, created at, and updated at. it is especially useful to locate a workflow before running or modifying it.
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.
Get All Users
This tool retrieves a list of all users within the organization from dailybot. it doesn't require any input parameters other than authentication. the returned json contains user details including uuid, active status, full name, and organizational data.
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.
Get Workflows List
This tool retrieves a list of all workflows that the authenticated user has access to in dailybot. it can be executed independently with only the authentication required, and it supports optional pagination parameters (page, per page) to refine the 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.
Give Kudos to Users
This tool allows giving kudos to one or multiple users in dailybot. kudos can be given either on behalf of dailybot or the api key owner.
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.
Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
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 Dailybot, 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 Dailybot.