Check vendor email changes before relying on them
A changed address can be easy to miss in a busy workspace. Have Notis ask Mails so to validate the vendor email when its Notion record is updated.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Validate Single Email
Tool to validate a single email address. use when you need to check deliverability and quality details before sending an email.
Why this helps
Small changes to vendor details can go unnoticed until a message bounces or a time-sensitive request gets delayed.
- Spot questionable updated addresses sooner.
- Keep a simple validation result alongside the record-change workflow.
- Avoid rechecking unchanged contacts manually.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mails so to Notis once through the portal.
- 2Create an automation with a plain-language instruction to validate the email on the changed vendor record and report its quality details.
- 3Select the Notion Page Properties Updated trigger for the vendor database.
- 4Choose a channel for run reports and test by updating one real vendor email.
Questions about this workflow
Can this check every property change?
The trigger can fire on property updates. Ask Notis in the prompt to validate the vendor email when the relevant contact record changes.
Will it overwrite the Notion record?
The selected action validates a single email. It does not write validation data back to Notion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mails so. A trigger fires from one place; an action lands in another.
Notion triggers
Mails so actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Retrieve Batch Results
Tool to retrieve results of a bulk validation job. use after submitting a batch and you have its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Validate Bulk Emails
Tool to validate multiple email addresses in bulk. use when you need to confirm deliverability of a list of emails at once.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Validate Single Email
Tool to validate a single email address. use when you need to check deliverability and quality details before sending an email.
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 Mails so, 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 Mails so.