Check a requested email address without leaving your GitHub task flow
When a teammate files a private, labeled GitHub issue with an address that needs checking, Notis can ask Mailcheck to verify it and return the result for review before you use it.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Verify Email Address
Tool to verify provided email address. use after obtaining user email input.
Why this helps
An address copied into a setup request can be mistyped, then cause avoidable delays when someone tries to use it later.
- Run a verification only for issues clearly labeled for an email check.
- Use the exact address in the issue instead of retyping it into another tool.
- Review the verification result before using the address for outreach or account setup.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mailcheck to Notis once, and use a private repository with access limited to people authorized to see the address.
- 2Create an automation in the portal or ask Notis conversationally; instruct it to verify only an address explicitly included in an issue carrying your email-check label.
- 3Select the new issue trigger, filter for the email-check label, and choose a channel for run reports.
- 4Test with an address you control and review the Mailcheck result in the run report before relying on it.
Questions about this workflow
Can this validate emails from public GitHub issues?
Do not put personal email addresses in public issues. Restrict this workflow to a private repository with appropriate access controls.
Will Mailcheck send an email to test the address?
The action is described as verifying the provided email address. It does not send an email as part of this workflow.
Does verification prove the person owns the address?
No. Treat the result as an email verification signal, not proof of identity or consent to contact the address.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mailcheck. A trigger fires from one place; an action lands in another.
GitHub triggers
Mailcheck actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Verify Email Address
Tool to verify provided email address. use after obtaining user email input.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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 Mailcheck, 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 Mailcheck.