Check the reach of a Notion prospect segment weekly
Have Notis revisit your Notion segment on a regular cadence and ask Hunter how many people are reachable across matching companies.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Count Reachable People
Estimate how many people are reachable across every company matching your filters.
Why this helps
A promising segment can become a stale assumption if nobody revisits its reachable audience as plans change.
- Establish a lightweight cadence for sizing prospect segments.
- Reduce repeated manual estimates when plans evolve.
- Support calmer prioritization with a consistent reachability check.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hunter to Notis once in the portal.
- 2Create an automation or ask Notis to check a Notion prospect segment every week.
- 3Describe which segment criteria to review and estimate in one plain-language prompt.
- 4Select a weekly recurring trigger and choose a channel for run reports.
- 5Test with one existing segment whose criteria are clear.
Questions about this workflow
What does the weekly action return?
Hunter estimates reachable people across companies matching the filters described in the automation.
Can I choose the day?
Choose the recurring schedule that fits your weekly planning routine.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hunter. A trigger fires from one place; an action lands in another.
Notion triggers
Hunter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Search People Across Companies
Search people across every matching company; addresses stay masked until revealed.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Count Reachable People
Estimate how many people are reachable across every company matching your filters.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search Companies
Search a B2B company database with structured filters like location, industry, and size.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Find Domain Emails
List all email addresses found for a domain, with sources and confidence scores.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Find Company Domain
Resolve a company name into its most likely domain name(s).
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Enrich Person and Company
Look up a person's profile and their company's profile from one email address.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion and Hunter, 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 Hunter.