Check partner contacts as they enter Notion
A partnership opportunity can involve many moving pieces. Let Notis ask Mailcheck to verify the email you capture for a new partner.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Verify Email Address
Tool to verify provided email address. use after obtaining user email input.
Why this helps
Partnership context can fade between discovery and follow-up, especially when address checking is left for later.
- Keep partnership contacts and email checks in the same intake flow.
- Reduce the delay between finding a partner and preparing follow-up.
- Avoid maintaining a separate mental list of addresses to verify.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailcheck to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Use one instruction to verify the email on a newly added partner contact record.
- 4Select New Page and scope it to your partner data source.
- 5Choose a channel for run reports and test with one real partner record.
Questions about this workflow
Does the workflow qualify a partnership lead?
No. It checks the provided email address. You decide whether the contact is a fit.
Can I use this for a general contacts database?
Yes, if you clearly describe in the prompt which records should be treated as partner contacts.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailcheck. A trigger fires from one place; an action lands in another.
Notion triggers
Mailcheck actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Verify Email Address
Tool to verify provided email address. use after obtaining user email input.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 Mailcheck, 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 Mailcheck.