Check imported event contacts in one pass
Imported contacts are easier to clean before they spread across your follow-up plan. Batch-check the list when it enters Notion.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Verify Batch Emails
Tool to verify a batch of up to 50,000 email addresses. use when you need bulk deliverability checks for many emails at once.
Why this helps
A fresh contact import can hide invalid addresses among useful leads, making later follow-up noisy and time-consuming.
- Check an imported list before planning individual follow-ups.
- See list-wide results in a batch workflow.
- Avoid repeatedly discovering address issues during outreach.
Setup
Build it in a few focused steps.
- 1Connect Notion and Emailable to Notis once through the portal.
- 2Create an automation prompting Notis to submit addresses from a newly created event contact list for batch verification.
- 3Choose Page Created scoped to the list's parent page or data source and select a channel for run reports.
- 4Create one test list with a small real set of event contacts.
Questions about this workflow
Is this suited to a large import?
Yes. Verify Batch Emails supports up to 50,000 email addresses per batch.
Will it start individual follow-up?
No. It only verifies the addresses and reports the batch result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Emailable. A trigger fires from one place; an action lands in another.
Notion triggers
Emailable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Info
Tool to retrieve account information including owner email and available credits. use when you need to confirm account status before sending email verifications.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Batch Status
Tool to get the status and results of a batch verification job. use after submitting a batch to check its progress.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Initiate OAuth Authorization
Tool to initiate oauth 2.0 authorization code flow. use when you need to obtain an authorization code from emailable. returns the url to redirect the user to.
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.
Verify Batch Emails
Tool to verify a batch of up to 50,000 email addresses. use when you need bulk deliverability checks for many emails at once.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Verify Email
Tool to verify a single email address and return detailed results. use when you need to check email deliverability and risk.
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 Emailable, 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 Emailable.