Keep incident response grounded in available capacity
When a security alert interrupts the day, make the supporting facts easy to retrieve.
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
Get Account Info
Tool to retrieve account information including owner email and available credits. use when you need to confirm account status before sending email verifications.
Why this helps
Incident response can scatter attention across tools, including checking whether a cleanup verification can run.
- Reduces tool switching during incidents
- Shows account owner and available credits
- Supports faster cleanup planning
Setup
Build it in a few focused steps.
- 1Connect GitHub and Emailable to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to retrieve Emailable account information whenever a new secret scanning alert is detected.
- 3Choose the secret scanning alert trigger and a reporting channel.
- 4Test with a safe test alert or run the automation with one real incident.
Questions about this workflow
Does this verify the leaked secret?
No. It retrieves Emailable account information to support the response workflow.
Why check credits?
Available credits help determine whether a planned contact-list verification can proceed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Emailable. A trigger fires from one place; an action lands in another.
GitHub triggers
Emailable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Info
Tool to retrieve account information including owner email and available credits. use when you need to confirm account status before sending email verifications.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Batch Status
Tool to get the status and results of a batch verification job. use after submitting a batch to check its progress.
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.
Initiate OAuth Authorization
Tool to initiate oauth 2.0 authorization code flow. use when you need to obtain an authorization code from emailable. returns the url to redirect the user to.
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.
Verify Batch Emails
Tool to verify a batch of up to 50,000 email addresses. use when you need bulk deliverability checks for many emails at once.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Verify Email
Tool to verify a single email address and return detailed results. use when you need to check email deliverability and risk.
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.
Connect any two apps with Notis in the middle.
GitHub and Emailable, or any other 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 Emailable.