Verify contact emails from new GitHub pull requests
Keep outreach tied to incoming code contributions without manually checking whether an address can receive mail.
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
Verify Email
Tool to verify a single email address in real-time. use when validating email entry form inputs instantly.
Why this helps
A useful contributor detail can disappear into a busy pull request queue before anyone validates the contact address.
- Reduces follow-up uncertainty
- Keeps contact checks near the pull request
- Saves a context switch
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bouncer to Notis once in the portal.
- 2Open Automations and create a new automation.
- 3Write a prompt asking Notis to verify any contact email mentioned in a new pull request.
- 4Select New Pull Request Created as the trigger and choose a report channel.
- 5Open one real pull request with a test address to confirm the result.
Questions about this workflow
Does this require field mapping?
No. Describe the outcome in one plain-language prompt and Notis handles the context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bouncer. A trigger fires from one place; an action lands in another.
GitHub triggers
Bouncer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Toxicity List Job Status
Tool to check the status of a specific toxicity list job. use after creating a toxicity list job to poll its status until completion.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Batch Request
Tool to initiate a batch email verification request. use when you have multiple emails to verify in one api call. returns a batch id and initial status.
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.
Create Toxicity List Job
Tool to create a toxicity analysis job for a list of email addresses. use when you need to batch-process toxicity checks for multiple emails at once.
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.
Delete batch request
Tool to delete a batch verification request. use when you need to remove all associated emails and results for a specific batch after confirming that the batch data is no longer required.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Toxicity List Job
Tool to delete a specific toxicity list job. use when you need to remove a completed or unwanted toxicity analysis job after confirming its id.
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.
Finish Batch
Tool to mark a batch verification process as finished. use after batch processing completes to stop further verifications and reclaim unused credits.
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.
Get Batch Results
Tool to retrieve the results of a batch verification process. use after submitting a batch to fetch all processed email verification outcomes.
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.
Verify Domain
Tool to verify the validity and configuration of a domain. use when you need to confirm the domain's mx records and catch-all behavior.
Connect any two apps with Notis in the middle.
GitHub and Bouncer, 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 Bouncer.