React faster to possible secret exposure
A GitHub secret alert should trigger a focused check of the web pages and notifications you monitor.
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 notifications
Tool to list account notifications. use after authenticating to retrieve notifications for one or all wachets within an optional time range.
Why this helps
A possible credential exposure creates urgent work that is easy to lose among normal development updates.
- Creates an immediate review habit for exposure events
- Keeps related web monitoring signals visible
- Helps founders act before a warning becomes a larger incident
Setup
Build it in a few focused steps.
- 1Connect GitHub and Wachete to Notis once through the portal.
- 2Create an automation and tell Notis: When GitHub detects a new secret scanning alert, list Wachete notifications and summarize anything that could indicate public exposure.
- 3Select the secret scanning trigger, choose a reporting channel, and test with one real alert.
Questions about this workflow
Can it remove the exposed secret?
No. It reviews Wachete notifications and reports context; remediation still happens in your security tools and repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Wachete. A trigger fires from one place; an action lands in another.
GitHub triggers
Wachete 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 Watcher
Tool to create a new watcher. use when setting up page monitoring after specifying url and xpath. confirm page url and xpath validity before running.
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 watcher
Tool to delete a watcher. use when you need to remove a monitor by its id after confirmation. confirm the watcher id is correct before calling. example: "delete watcher with id 123abc."
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 folder content
Tool to retrieve the content of a folder. use when you need to list subfolders and watchers inside a specific folder after managing folder structure.
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 notifications
Tool to list account notifications. use after authenticating to retrieve notifications for one or all wachets within an optional time range.
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 watchers
Tool to list all watchers. use when you need to retrieve your configured monitoring tasks.
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 Wachete. 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 Wachete.