Review your Findymail contact lists every week
Set aside one small recurring check so contact lists stay understandable without constant monitoring.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Contact Lists
Tool to retrieve all contact lists. use when you need an overview of your existing findymail lists.
Why this helps
When lists multiply quietly, founders lose track of which audience is current and which follow-up is next.
- Creates a predictable review rhythm
- Reduces list clutter anxiety
- Keeps outreach planning visible
Setup
Build it in a few focused steps.
- 1Connect Findymail to Notis once; GitHub can also stay connected for related workflows.
- 2Create an automation and write a plain-language instruction to retrieve and summarize your Findymail contact lists weekly.
- 3Pick a weekly recurring schedule, choose a report channel, and test one run.
Questions about this workflow
Does this change any lists?
No. This workflow retrieves an overview so you can decide what needs attention.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Findymail. A trigger fires from one place; an action lands in another.
GitHub triggers
Findymail actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact List
Tool to create a new contact list. use when you need to organize contacts into a named list before adding them.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Contact List
Tool to delete a specified contact list by its id. use after confirming the list id to remove it.
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.
Find Email by Name
Tool to find someone's email using their full name and company domain. use when you have a person's name and domain and need their email address. supports asynchronous search via webhook url.
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.
Get Contact Lists
Tool to retrieve all contact lists. use when you need an overview of your existing findymail lists.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Contacts
Tool to retrieve contacts from a specified list (paginated). use after selecting a list to fetch its contacts.
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.
Verify Email
Tool to verify the deliverability of an email address. use when you need to confirm that an email can receive messages before outreach.
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 Findymail, 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 Findymail.