Prepare a Benchmark Email list for a GitHub cohort
When a new pull request marks a new review or launch cohort, create a dedicated Benchmark Email list so you have a place to organize its contacts.
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
Create Contact List
Tool to create a new contact list. use after planning list name and optional description.
Why this helps
Setting up a cohort list by hand adds another small task to an already busy review or launch process.
- Create a list when a qualifying PR appears
- Use a consistent name based on details available in the PR
- Keep cohort setup from becoming a separate reminder
Setup
Build it in a few focused steps.
- 1Connect GitHub and Benchmark Email to Notis once.
- 2Create an automation in Notis and give it a clear name.
- 3Describe in one instruction which new pull requests qualify and how to name the contact list.
- 4Pick the New Pull Request Created trigger and choose where run reports should go.
- 5Test with one real qualifying pull request and confirm the list was created.
Questions about this workflow
Will this add people to the new list?
No. The Create Contact List action creates the list only. Adding contacts requires their email addresses and a separate Add Contact to List action.
Can it infer the cohort name?
It can use information present in the pull request, such as its title or branch, if you state the naming rule. Any extra naming context must be supplied in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Benchmark email. A trigger fires from one place; an action lands in another.
GitHub triggers
Benchmark email actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Contact From List
Tool to delete a contact from a specific list by contactid. use when you have list and contact ids. example: "delete contact 2040826674 from list 15257899"
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Contact List
Tool to delete a contact list. use after confirming that the list is no longer in use.
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.
Delete Email Campaign
Tool to delete an email campaign. use when removing a campaign by its id. use after confirming the campaign id is correct.
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 Linked Agency Account
Tool to delete a linked agency account. use when revoking a linked agency account by its id. use after confirming the account id is correct.
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 Webhook
Tool to delete a webhook from a contact list by its id. use when removing obsolete or invalid webhooks after confirming list and webhook details.
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.
Get All Confirmed Emails
Tool to retrieve all confirmed email addresses for the client account. use after user completes email confirmation flows to fetch final list.
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 Client Account Settings
Tool to get client account settings such as company, language, timezone, and sender info. use when you need to fetch account configuration before sending campaigns.
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.
Get client details
Tool to get client details including profile data, contact count, and plan information. use when verifying account profile and limits.
Connect any two apps with Notis in the middle.
GitHub and Benchmark email, 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 Benchmark email.