Give secret scanning alerts a fast first read
A secret alert needs a calm, immediate response, not a delayed investigation.
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
/v1/cve
Why this helps
Founders may see a credential alert without enough context to judge exposure quickly.
- Surfaces related vulnerability information
- Supports faster response decisions
- Keeps alert handling consistent
Setup
Build it in a few focused steps.
- 1Connect GitHub and api.kadec0.xyz to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Tell Notis: When GitHub detects a new secret scanning alert, use the CVE tool to research related technology and return concise response guidance.
- 4Select the secret scanning trigger and choose where run reports should arrive.
- 5Test with one real alert.
Questions about this workflow
Will it revoke the secret?
No. It researches context and reports guidance; revocation remains a deliberate human action.
Can it handle different secret types?
Yes, the instruction can ask Notis to tailor the research to the alert details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to api.kadec0.xyz. A trigger fires from one place; an action lands in another.
GitHub triggers
api.kadec0.xyz 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.
/v1/youtube
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.
/v1/serp-batch
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
/v1/scrape
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.
/v1/enrich
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.
/v1/serp-read
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.
/v1/cve
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 api.kadec0.xyz. 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 api.kadec0.xyz.