Turn audit findings into a build
Send a 21risk audit finding to Notis and kick off the CircleCI pipeline that helps you address it.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Trigger Pipeline
Tool to trigger a new pipeline for the specified project. use when you need to start a build on a branch or tag programmatically.
Why this helps
Audit findings can sit in a checklist while the code change needed to resolve them waits for someone to start a build.
- Start remediation work without manually switching to CircleCI.
- Keep the audit finding as the context for the build request.
- Reduce delays between identifying a code issue and beginning a fix.
Setup
Build it in a few focused steps.
- 1Connect 21risk and CircleCI once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to start a CircleCI pipeline when a webhook reports a 21risk audit finding that needs a code change.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real audit finding sent to the webhook.
Questions about this workflow
Does 21risk trigger this workflow directly?
21risk has no trigger event listed here. The workflow starts when a webhook request reaches Notis, carrying the audit finding context.
Does this workflow fix the finding?
No. It starts a CircleCI pipeline. The code change and any later audit update remain separate work.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Circleci. A trigger fires from one place; an action lands in another.
21risk triggers
Circleci actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Job Artifacts
Tool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Job Details
Tool to fetch details of a specific job within a project. use when you need status, timing, and executor information for a circleci job by its number.
Get Pipeline Config
Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
Get Test Metadata
Tool to fetch test metadata for a specific job. use when you need detailed test results, run times, and failure messages after a job completes.
Get User Information
Tool to retrieve information about a circleci user by their unique id. use when you need user profile details after obtaining the user id.
List Pipelines for Project
Tool to list all pipelines for a specific project. use when you need to retrieve the pipelines for a project (e.g., to display recent runs on a dashboard).
List Self-Hosted Runners
Tool to list available self-hosted runners. use when you need to retrieve all configured self-hosted runners for your organization.
List Workflows by Pipeline ID
Tool to list all workflows associated with a specific pipeline. use when you need to fetch or paginate through workflows by pipeline id.
Connect any two apps with Notis in the middle.
21risk and Circleci, 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 Circleci.