Check vendor contacts when you add them
A new vendor record can trigger an email check while the reason you captured that contact is still clear.
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
Vendor details often arrive amid other operational tasks, leaving validation as another thing to remember.
- Put vendor address checking into the intake moment.
- Reduce deferred verification tasks on an already busy operations list.
- Keep the original vendor context close to the check.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailcheck to Notis once through the portal.
- 2Create an automation by asking Notis conversationally or using the portal.
- 3Give Notis one instruction to verify the email on new vendor records with Mailcheck.
- 4Choose New Page and select the vendor data source as its scope.
- 5Select a report channel and test with one new vendor record.
Questions about this workflow
Can I use this for a vendor database?
Yes. Scope the New Page trigger to the data source where vendor records are created.
Does verification mean the vendor address belongs to the right person?
Verification checks the provided address according to Mailcheck. It does not independently confirm the identity of its owner.
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.