Check CircleCI runners after a secret alert
Make urgent remediation planning start with a clear view of available build capacity.
Trigger
New Secret Scanning Alert Detected
Triggers when a new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filtering by secret type (e.g., personal access tokens, AWS keys) and by token validity status (active, inactive, unknown). The payload includes the alert number, secret type, validity status, resolution state, timestamps, URLs, and flags for push protection bypass, public exposure, and multi-repo detection.
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
A security alert creates urgency, but the next operational step is often unclear.
- Provides immediate capacity context
- Supports a more deliberate response
Setup
Build it in a few focused steps.
- 1Connect GitHub and CircleCI to Notis once in the portal.
- 2Create a new automation in Automations.
- 3Tell Notis to list CircleCI self-hosted runners when a GitHub secret alert is detected, select the secret-alert trigger and a secure reporting channel, then test with a safe example.
Questions about this workflow
Does this expose a secret?
The automation uses the alert event to request runner availability; keep reports in an appropriate channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Circleci. A trigger fires from one place; an action lands in another.
GitHub 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.
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 Pipeline Config
Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
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 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.
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 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.
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.
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).
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.
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.
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.
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.
GitHub 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.