Find contact details from updated prospect notes
When you add the missing company or name to prospect notes, let Findymail take the next email lookup step.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
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.
Why this helps
Research notes often become actionable only after you add one missing detail, and that moment can pass unnoticed.
- Continue research when key prospect details are added to notes.
- Avoid revisiting a page just to remember what to do next.
- Use the page as the context for a name-and-domain lookup.
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 look up prospect emails when their notes are updated.
- 3Write one plain-language instruction to use the updated notes to identify a full name and company domain for Findymail.
- 4Choose Page Content Updated and a channel for run reports, then test by updating one real prospect page.
Questions about this workflow
Can this trigger be limited to one page or database?
Page Content Updated supports optional page, parent page, or data source scope when setting up the trigger.
What if the notes do not have both lookup details?
The prompt should tell Notis to proceed only when the notes provide a full name and company domain.
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.