Make check results easier to act on
A check result is more useful when the next communication step is visible.
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 Document Exports
Tool to retrieve a paginated list of document exports. use after initiating export jobs to fetch export history.
Why this helps
Check results can be acknowledged technically while related documentation, reports, or announcements remain unattended.
- Pair check conclusions with a content review moment.
- Highlight follow-up after failures or important successes.
- Reduce scattered post-check decisions.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cloudpress to Notis once through the portal.
- 2Create the automation or ask Notis to review Cloudpress exports whenever a GitHub check run changes conclusion and summarize the next content action.
- 3Choose the check run status trigger and the channel for run reports.
- 4Test with one completed check run.
Questions about this workflow
Can it focus on failed checks?
Yes. Tell Notis to prioritize failed, timed out, or action-required conclusions.
Will it rerun the check?
No. It reviews Cloudpress exports based on the check event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Cloudpress. A trigger fires from one place; an action lands in another.
GitHub triggers
Cloudpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Information
Tool to retrieve authenticated account information. use after authentication to get current account details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Connections
Tool to list all connections with pagination. use when you need to retrieve cloudpress connections page by page with optional filters like kind, type, or sourcereference.
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 Document Exports
Tool to retrieve a paginated list of document exports. use after initiating export jobs to fetch export history.
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 Webhooks
Tool to retrieve a paginated list of webhooks. use when you need an overview of all configured webhooks.
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 Cloudpress, 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 Cloudpress.