Make secret-alert response more coordinated
A sensitive alert can automatically bring the affected product workspace into the response conversation.
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 Modelry Workspaces
Tool to list all workspaces in modelry. use when you need to retrieve available workspaces after authenticating.
Why this helps
Secret exposure requires fast action, but product ownership and related work may be scattered across separate systems.
- Reduces time spent identifying affected product context
- Supports faster coordinated response
- Keeps security follow-up connected to operational work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Modelry to Notis once.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Describe the outcome: when a new GitHub secret-scanning alert is detected, list the Modelry workspaces connected to the affected product and report the alert context without exposing the secret value.
- 4Select the secret-alert trigger, choose a reporting channel, and test with one safe example.
Questions about this workflow
Will the secret itself be included in the report?
Tell Notis not to reproduce secret values; the workflow only needs alert metadata and workspace context.
Can it focus on active secrets?
Yes. Configure the trigger or instruction to focus on the validity status that requires action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Modelry. A trigger fires from one place; an action lands in another.
GitHub triggers
Modelry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Workspace
Tool to create a new workspace. use when you need to group products and embeds into a dedicated workspace. call after authenticating and specifying workspace details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Modelry Embed
Tool to delete an embed. tries multiple common endpoint patterns and treats 404 as idempotent success after exhausting candidates (embed already deleted or not found).
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.
Delete Modelry Product
Tool to delete a product. use after confirming the product id.
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.
Delete Product Repository
Tool to delete a product repository. use after confirming the repository id.
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 Modelry Workspace
Tool to delete a workspace. use after confirming the workspace 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.
Get Embed
Tool to retrieve details of a specific embed. use after confirming the embed id.
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 Product Repository
Tool to retrieve details of a specific product repository. use when you have a repository id and need its details.
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.
Get Workspace
Tool to retrieve details for a specific workspace. use after confirming the workspace id.
Connect any two apps with Notis in the middle.
GitHub and Modelry, 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 Modelry.