Check a contact email when a data source is added
Adding a data source can trigger a focused check on the relevant contact email in the setup context, with results reported by Notis.
Trigger
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.
Action
Check Email Validity
Tool to validate a single email address. use when you need to check syntax, domain, smtp, and meta-flags.
Why this helps
A newly added data source can sit outside established review habits while you adapt your workspace.
- Provide an email review cue when a data source is introduced.
- Keep setup work connected to contact quality.
- Avoid relying on memory for an initial validation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailboxlayer to Notis once in the portal.
- 2Create the automation through the portal or ask Notis in plain language.
- 3In one instruction, tell Notis which available contact email to check when a data source is added and how to report the result.
- 4Select Data Source Created and choose a channel for run reports.
- 5Test with one real data source creation event and relevant address context.
Questions about this workflow
Is this different from Database Created?
Yes. Data Source Created fires when a data source is added, including to an existing database.
Can one template generate multiple runs?
Yes. A template-based database creation can produce multiple data source created events.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailboxlayer. A trigger fires from one place; an action lands in another.
Notion triggers
Mailboxlayer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Email Validity
Tool to validate a single email address. use when you need to check syntax, domain, smtp, and meta-flags.
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 Mailboxlayer, 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 Mailboxlayer.