Create a BigML response project for secret alerts
Turn an exposed-secret notification into an organized next step.
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
Create Project
Tool to create a new project. use when you need to group related bigml resources into a project.
Why this helps
Security notifications are easy to defer when there is no clear workspace for the response.
- Creates a clear response boundary
- Keeps data-work follow-up visible
- Reduces repeated setup work
Setup
Build it in a few focused steps.
- 1Connect GitHub and BigML to Notis once.
- 2Create an automation in the portal.
- 3Tell Notis to create a response project for every new secret scanning alert.
- 4Select New Secret Scanning Alert Detected and a report channel.
- 5Trigger a safe test alert and review the report.
Questions about this workflow
Will Notis expose secret values?
The automation can be described to focus on the alert and response workspace rather than handling secret contents.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bigml. A trigger fires from one place; an action lands in another.
GitHub triggers
Bigml actions
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.
Create External Connector
Tool to create a new external connector for data sources. use after configuring external databases or search indices.
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.
Create Project
Tool to create a new project. use when you need to group related bigml resources into a project.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Project
Tool to delete an existing project. use when you need to permanently remove a project resource after confirming it is not in use by other resources.
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.
Get External Connector
Tool to retrieve details of an external connector. use after creating or listing external connectors to inspect its state.
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.
Get Project
Tool to retrieve details of a project by id. use when you need to inspect project metadata before analysis.
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 Correlations
Tool to list correlation resources. use when you need to browse or paginate existing correlations for the authenticated user.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Bigml. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Bigml.