Gather cluster context for a new secret scanning alert
When GitHub detects a secret, get the Bonsai cluster details you identify in your instruction and bring that context into the alert response.
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
Get Bonsai Cluster Details
Tool to retrieve details for a single bonsai cluster by slug. use when you need to inspect a cluster's configuration and status.
Why this helps
Responding to a sensitive alert is harder when relevant system details must be gathered from another app by hand.
- Gather cluster context at alert time
- Reduce manual app switching during security follow-up
- Use a specific cluster slug to focus the lookup
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bonsai once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe which Bonsai cluster to inspect when GitHub detects a new secret scanning alert.
- 4Pick the new secret scanning alert detected trigger and choose where run reports go.
- 5Test with one real alert and confirm the report returns the intended cluster details.
Questions about this workflow
Can I filter the alert types?
The trigger supports filters such as secret type and token validity status.
Will this rotate a credential or close the alert?
No. The available Bonsai action retrieves cluster details only; it does not manage GitHub alerts or credentials.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bonsai. A trigger fires from one place; an action lands in another.
GitHub triggers
Bonsai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Bonsai Cluster Details
Tool to retrieve details for a single bonsai cluster by slug. use when you need to inspect a cluster's configuration and status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Bonsai Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available to your account.
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.
Retrieve Space Details
Tool to retrieve details for a single space by its path. use when you need metadata for a space before provisioning a cluster. use after confirming this detail exists. e.g., 'omc/bonsai/us-east-1/common'.
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.
List Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available for your account.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Bonsai, 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 Bonsai.