Verify New Lead Emails Before Outreach
Add a lead in Notion and have its email checked right away, so you can focus follow-up on addresses that look deliverable.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Verify Email
Tool to verify a single email address in real time. use when you need to confirm deliverability before e.g. user signup.
Why this helps
Manual checks add another step between capturing a lead and acting on it, making outreach easier to postpone.
- Catch likely invalid addresses while the lead is fresh.
- Reduce tab switching between your CRM and validation tools.
- Make the next outreach decision with more confidence.
Setup
Build it in a few focused steps.
- 1Connect Notion and Emaillistverify to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to set it up in plain language.
- 3In one instruction, ask Notis to verify the email on each new lead page and report the result.
- 4Choose the Notion New Page trigger and a channel for run reports.
- 5Test with one real lead record that has an email address.
Questions about this workflow
What starts this automation?
A new page added to the Notion database you choose as the trigger source.
Does it verify every email on the page?
Emaillistverify's single-email action checks one address per run. Tell Notis which email on the new lead record to check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Emaillistverify. A trigger fires from one place; an action lands in another.
Notion triggers
Emaillistverify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Verify Email
Tool to verify a single email address in real time. use when you need to confirm deliverability before e.g. user signup.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Verify Email Detailed
Tool to verify a single email address and return detailed validation information. use when you need deep validation insights beyond a simple status.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 Emaillistverify, 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 Emaillistverify.