Check changed contact emails across your workspace
A broad page event can help catch email details updated in different parts of your workspace, with the prompt focused on relevant contact changes.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
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.
Why this helps
Contact details can live across projects and notes, making it hard to remember where an address was changed.
- Use one event to notice relevant contact changes across accessible pages.
- Reduce the need to remember which project contains a person's details.
- Keep verification requests connected to the source page.
Setup
Build it in a few focused steps.
- 1Connect Notion and Findymail to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to check contact emails when relevant Notion pages change.
- 3Write one plain-language instruction to identify changed contact email details and verify them with Findymail.
- 4Choose All Page Events and a channel for run reports, then test with one real contact update.
Questions about this workflow
Will this use Findymail for every page event?
Describe in the prompt that Notis should act only when a relevant contact email is present or changed.
Is this best for a large workspace?
A workspace-wide event may be broad. A scoped Page Properties Updated or Page Content Updated trigger may suit a focused database or page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Findymail. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
Get Contact Lists
Tool to retrieve all contact lists. use when you need an overview of your existing findymail lists.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Contacts
Tool to retrieve contacts from a specified list (paginated). use after selecting a list to fetch its contacts.
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.
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.
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 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.