Catch failed GitHub checks early
A broken check should interrupt you once, clearly, and at the right moment.
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
Send Message
Tool to send a push notification with optional title, URL, priority, sound, attachments, and filters.
Why this helps
Failed checks are easy to miss when CI feedback is scattered across pull requests.
- Spot blockers without refreshing GitHub
- Focus only on actionable failures
- Reach release decisions faster
Setup
Build it in a few focused steps.
- 1Connect GitHub and Pushover to Notis once.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Use this instruction: Send a high-priority Pushover alert when the monitored GitHub check run reaches a failed, cancelled, timed out, or action required conclusion, with the check name and link.
- 4Select the check-run status trigger and choose the run-report channel.
- 5Test it with one real failed check.
Questions about this workflow
Can successful checks be ignored?
Yes. Tell Notis to alert only for the failure conclusions that matter to you.
Can I make the notification urgent?
Yes. Ask Notis to use an urgent Pushover priority when the failure blocks a release.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Pushover. A trigger fires from one place; an action lands in another.
GitHub triggers
Pushover 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.
Cancel Receipt Retries
Tool to cancel further retries for an emergency-priority message before its expiry. Use when you no longer want Pushover to keep attempting delivery of an urgent notification.
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.
Cancel Retries by Tag
Tool to cancel retries for all active emergency-priority Pushover messages matching a specific tag. Use after sending emergency messages when you want to stop further retries for a given tag.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Client Acknowledge Delete Up To ID
Tool to delete/acknowledge device messages up to a specific message ID. Use when you want to clear all messages up to a known ID; call after retrieving the latest message ID.
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.
Fetch Pending Messages
Tool to download pending messages for a registered device. Use after device registration to retrieve messages queued server-side.
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.
Pushover Client Login
Tool to authenticate a Pushover user by email and password. Use when you need to obtain a user key and session secret. Include twofa code if prompted by a prior HTTP 412 response.
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.
Client Realtime WebSocket Connection
Tool to establish a secure WebSocket connection for real-time message notifications. Use after obtaining device ID and secret to receive instant push events.
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.
Register Open Client Device
Tool to register an Open Client desktop device. Use when you have a session secret from users/login to obtain a device ID.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Application Icon Image
Tool to fetch an application icon PNG by icon identifier. Use when you need to retrieve and cache the Pushover app icon image.
Connect any two apps with Notis in the middle.
Not just GitHub and Pushover. 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 Pushover.