Know which self-hosted runners are available
Get a scheduled view of configured CircleCI self-hosted runners while you coordinate compliance-related build work.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
Build preparation can stall when runner availability is unclear and the team discovers it only after trying to start work.
- Retrieve the configured self-hosted runners for your organization.
- Keep runner readiness on a regular review cadence.
- Make infrastructure follow-up easier to spot alongside compliance work.
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 the organization's configured self-hosted runners and report the returned availability information alongside the 21risk work you specify.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real runner inventory review.
Questions about this workflow
Does the action report whether a runner is currently online?
It lists available self-hosted runners as described by the action. The exact fields returned determine what availability details can be reported.
Does this start a build?
No. This workflow retrieves runner information for review; it does not trigger a CircleCI pipeline.
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.