Check supplied email addresses on new pull requests
New pull requests create a natural moment to check an available author email before it gets reused elsewhere.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
Instant Email Verifier
Tool to instantly verify a single email address. Use when you need real-time validation before processing an email.
Why this helps
Pull request follow-up gets harder when contact information is scattered across repository activity and separate tools.
- Verify an available email when a new pull request is created.
- Avoid manually moving addresses between GitHub and Clearout.
- Keep the verification result with the automation run report.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Clearout once in the Notis portal.
- 2Create an automation in Automations, then choose a name and prompt.
- 3Tell Notis to verify any author email included with each new pull request.
- 4Pick the New Pull Request Created trigger, choose a report channel, and test with one real pull request.
Questions about this workflow
Will every pull request have an email to verify?
Not necessarily. The workflow can only verify an address included in the available event data.
Does this send an email to the author?
No. Clearout verifies the supplied address; this action does not send a message.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Clearout. A trigger fires from one place; an action lands in another.
GitHub triggers
Clearout actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Autocomplete Company to Domain
Tool to autocomplete company names to probable domains with confidence scores. Use after obtaining a company name or URL to get suggestions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Business Account Verify
Tool to check if an email belongs to a business/work account. Use when validating corporate emails before onboarding.
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.
Catch-All Verify
Tool to check if an email domain is catch-all. Use after confirming email validity.
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 Disposable Email
Tool to check if an email is from a disposable provider. Use after acquiring an email address.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Find Domain MX Records
Tool to retrieve MX records for a domain in priority order. Use when you need to find a domain's mail servers (e.g., for email routing setup).
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.
Fetch Domain WHOIS Information
Tool to fetch WHOIS record for a domain. Use when you need WHOIS data for a domain.
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.
Bulk Email Finder
Tool to upload a CSV or XLSX contacts file for bulk email finding. Use when you need to find emails for a list of contacts in bulk.
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.
Cancel Bulk Email Finder Job
Tool to cancel a running bulk email finder job. Use when you need to stop an in-progress list scan before completion.
Connect any two apps with Notis in the middle.
GitHub and Clearout, 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 Clearout.