Connect code scanning alerts to risk models
Replace a frantic search for policy with the right risk-model context.
Trigger
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.
Action
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.
Why this helps
Founders lose momentum when every vulnerability requires hunting for the applicable standard.
- Makes policy context easier to find
- Supports consistent triage
Setup
Build it in a few focused steps.
- 1Connect GitHub and 21risk once.
- 2Create a new portal automation.
- 3Ask Notis to retrieve applicable 21risk risk models for each new GitHub code scanning alert.
- 4Pick the code scanning alert trigger and your reporting channel.
- 5Test with a real finding.
Questions about this workflow
Can this fix the vulnerability?
It retrieves risk-model context; remediation remains with your engineering process.
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
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 Compliance
Tool to retrieve compliance data for sites, categories, or questions. use when you need odata-based compliance data for analytics or reporting.
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 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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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).
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 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.
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 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.
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 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.
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.
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).
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and 21risk. 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 21risk.