Check certificate monitoring after a secret alert
A new secret alert should trigger a quick look at certificate coverage, not another forgotten security task.
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 Monitored Domains
Tool to list all monitored domains. use when you need to audit or review the domains currently monitored by cert spotter.
Why this helps
Security alerts create urgent context switching and make it easy to overlook whether the exposed product domain is being watched.
- Creates an immediate domain coverage check
- Keeps security follow-up in one automation
- Reduces manual dashboard hopping
Setup
Build it in a few focused steps.
- 1Connect GitHub and Sslmate cert spotter api to Notis once.
- 2Create an automation in the portal or ask Notis to create one in plain language.
- 3Use this instruction: When a new GitHub secret scanning alert appears, list the CertSpotter monitored domains and report the result with the alert link.
- 4Choose the GitHub secret scanning alert trigger and a run-report channel, then test with one real alert.
Questions about this workflow
Does this expose the secret value?
No. The automation asks CertSpotter for monitored-domain coverage and reports the GitHub alert context, not secret contents.
What does CertSpotter return?
It returns the currently monitored domains so you can check whether the relevant surface is covered.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Sslmate cert spotter api. A trigger fires from one place; an action lands in another.
GitHub triggers
Sslmate cert spotter 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.
Get CertSpotter Event
Tool to retrieve detailed information about a specific certspotter event. use when you need to inspect event metadata after confirming an event 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.
List Monitored Domains
Tool to list all monitored domains. use when you need to audit or review the domains currently monitored by cert spotter.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Retrieve Webhook Settings
Tool to retrieve webhook settings. use when you need to view the currently configured cert spotter webhook.
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 Sslmate cert spotter 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 Sslmate cert spotter api.