Start a new email tracker with an MX lookup
Create a Notion data source for email setup and prompt an MX record lookup to help start the domain review.
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
Lookup MX Records
Tool to retrieve mx records for a given domain. use when you need to discover mail exchange servers after obtaining a domain.
Why this helps
A new tracking system can take effort to organize while the first practical checks are still waiting to be done.
- Pair a new email setup tracker with a concrete routing check.
- Reduce the gap between organizing work and beginning it.
- Keep the result available in a chosen channel.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mx toolbox to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give Notis one plain-language instruction to retrieve MX records for the email domain associated with a newly created setup data source and report the result.
- 4Choose the Notion Data Source Created trigger and a run-report channel.
- 5Test by creating a real email setup data source with a clear domain reference.
Questions about this workflow
Does this create a Notion database?
No. It responds when a Notion data source is created and retrieves MX records.
What if the new source does not identify a domain?
Include clear domain context in the source or automation prompt so Notis can determine what to check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mx toolbox. A trigger fires from one place; an action lands in another.
Notion triggers
Mx toolbox actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Lookup BIMI Record
Tool to retrieve bimi (brand indicators for message identification) record for a domain. use when checking domain brand identity via bimi lookup.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Lookup Blacklist
Tool to perform a blacklist check on a domain or ip. use when you need to verify whether a domain or ip is listed in common blacklists.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Lookup DKIM Record
Tool to retrieve dkim records for a domain. use when verifying dkim configuration before sending 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.
Lookup DMARC Record
Tool to retrieve dmarc records for a domain. use after confirming the domain is correctly formatted.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Lookup DNS Records
Tool to retrieve dns records for a given domain. use when you need dns lookup details.
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.
HTTP Lookup
Tool to perform an http test on a domain. use when you need to assess http connectivity and status for a given domain.
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.
Lookup MTA-STS Record
Tool to lookup mta-sts record for a domain. use when validating mail transport security policy.
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.
Lookup MX Records
Tool to retrieve mx records for a given domain. use when you need to discover mail exchange servers after obtaining a domain.
Connect any two apps with Notis in the middle.
Notion and Mx toolbox, 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 Mx toolbox.