See test failures in audit context
Bring completed-job test details into the same review flow as the 21risk finding that prompted the fix.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A finished remediation build can still leave you hunting through CircleCI to understand which tests failed and why.
- Retrieve test timing and failure messages after a job completes.
- Keep review focused on a specific remediation job.
- Reduce manual searching after a build finishes.
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 retrieve test metadata for the completed CircleCI job when a webhook reports that a 21risk remediation build is ready for review.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real completed job and its related audit context.
Questions about this workflow
What does the CircleCI action return?
It retrieves test metadata for a specific job, including available test results, runtimes, and failure messages.
Will Notis know the job number automatically?
The webhook request or your instruction must provide enough context to identify the specific job. The listed action fetches metadata for a specific job.
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.