Check Zyte incidents after a GitHub secret alert
Get vendor context without losing your place in secret remediation.
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
Zyte API: Get Unresolved Incidents
Tool to retrieve unresolved incidents from zyte status api. use when you need to check currently open incidents.
Why this helps
Urgent secret alerts make it easy to overlook a separate service issue affecting remediation work.
- Reduces tab switching during remediation
- Surfaces active Zyte incidents early
Setup
Build it in a few focused steps.
- 1Connect GitHub and Zyte api once.
- 2Create a new automation from the portal.
- 3Describe: When a secret scanning alert is detected, list unresolved Zyte API incidents and notify me.
- 4Choose New Secret Scanning Alert Detected and a channel.
- 5Test it with a real alert.
Questions about this workflow
Will this expose the secret?
No. The automation requests Zyte incident status for your report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Zyte api. A trigger fires from one place; an action lands in another.
GitHub triggers
Zyte api 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.
Fetch Active Scheduled Maintenances
Tool to fetch currently active scheduled maintenances. use when you need to know ongoing maintenance events.
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.
Get scheduled maintenances
Tool to get the 50 most recent scheduled maintenances (upcoming and completed) from zyte status api. use after confirming you need the latest maintenance schedule for monitoring.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Zyte API: Get Unresolved Incidents
Tool to retrieve unresolved incidents from zyte status api. use when you need to check currently open incidents.
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 Zyte API status incidents
Tool to list the 50 most recent incidents on the zyte api status page. use after needing current api health or incident summaries.
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.
Zyte Status Summary
Tool to get a summary of status indicators, component statuses, unresolved incidents, and scheduled maintenances. use when you need an overview of the current zyte service health.
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.
Upcoming Scheduled Maintenances
Tool to retrieve upcoming scheduled maintenance windows. use when you need to list upcoming maintenance events from the zyte api status page.
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.
Zyte API Components
Tool to fetch the list of zyte api service components and their statuses. use when you need a current snapshot of component health from the zyte status page.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Zyte API Status Rollup
Tool to retrieve the overall status rollup for the zyte api. use when you need a current summary of service health before proceeding.
Connect any two apps with Notis in the middle.
Not just GitHub and Zyte api. 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 Zyte api.