Keep secret scanning response visible
A newly detected secret immediately creates a visual handoff for the response work that follows.
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
Screenshot API
Tool to capture a screenshot of a webpage. use when you need a visual snapshot of a page; supports full-page, device emulation, delays, and dark mode.
Why this helps
Secret alerts require fast action, but the response checklist and exposure context can disappear beneath unrelated notifications.
- Make urgent response work harder to overlook
- Preserve the relevant exposure context
- Support a repeatable credential-rotation routine
Setup
Build it in a few focused steps.
- 1Connect GitHub and Serpdog to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Give Notis one instruction to screenshot the secret-response webpage whenever a new secret scanning alert is detected.
- 4Choose the GitHub secret scanning trigger and select the reporting channel.
- 5Test with a safe test alert or verify against one real alert.
Questions about this workflow
Will the secret value appear in the screenshot?
Configure the instruction to capture only the alert or remediation page and never expose secret values.
Can the workflow focus on active tokens?
Yes. Mention the desired validity status in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Serpdog. A trigger fires from one place; an action lands in another.
GitHub triggers
Serpdog 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.
Screenshot API
Tool to capture a screenshot of a webpage. use when you need a visual snapshot of a page; supports full-page, device emulation, delays, and dark mode.
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.
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.
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 Serpdog. Any 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 Serpdog.