Retrieve audit reports after a check run changes
Pair a failing check with the audit context needed for an intentional next step.
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
Get Reports
Tool to retrieve audit reports, including draft, published, and scheduled reports. use when you need a paginated list of reports with optional odata filtering.
Why this helps
A failed check can cause reactive work without anyone checking the broader audit picture.
- Supports thoughtful failure follow-up
- Keeps audit context close
Setup
Build it in a few focused steps.
- 1Connect GitHub and 21risk once.
- 2Open Automations and create a new automation.
- 3Ask Notis to retrieve relevant audit reports when a monitored GitHub check run changes conclusion.
- 4Select the check-run trigger and run-report channel.
- 5Test with one check run.
Questions about this workflow
Which conclusions can trigger it?
The trigger monitors status and conclusions including success, failure, cancelled, timed out, and action required.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to 21risk. A trigger fires from one place; an action lands in another.
GitHub triggers
21risk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Compliance
Tool to retrieve compliance data for sites, categories, or questions. use when you need odata-based compliance data for analytics or reporting.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Items (BETA)
Tool to retrieve items (beta) from the 21risk odata api. use when you need a filtered and paged list of items for analytics and reporting. example: get items($filter="item cost gt 100", $top=50).
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 Items Per Month
Tool to retrieve fact table data for itemspermonth, one row per question per site per month. use when querying monthly item data with odata parameters ($filter, $top, $skip, $select, maxpagesizeinmb).
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 Organizations
Tool to retrieve organizations from the 21risk odata api. use when you need to list, filter, or paginate organizations via odata parameters after authentication is confirmed.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Properties
Tool to fetch a list of properties related to sites, including cope information and other relevant data. use when you need property insurance details via odata api after authentication.
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.
Get Reports
Tool to retrieve audit reports, including draft, published, and scheduled reports. use when you need a paginated list of reports with optional odata filtering.
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.
Get RiskModel Categories
Tool to retrieve risk model categories for grouping questions and compliance checks. use when you need to filter, select, or paginate risk model categories via odata parameters ($filter, $select, $orderby, $top, $skip, $count).
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.
Get Risk Models
Tool to retrieve risk models used for audits and compliance. use when you need to list available risk models with optional odata queries.
Connect any two apps with Notis in the middle.
GitHub and 21risk, 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 21risk.