Verify a domain when you add it to Notion
Give a new sending domain a configuration check before it becomes part of your workflow.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Verify Domain
Tool to verify the validity and configuration of a domain. use when you need to confirm the domain's mx records and catch-all behavior.
Why this helps
A domain added to setup notes can be mistaken for a domain that is already ready to use.
- Check new domains as soon as they are recorded.
- Catch configuration issues before relying on the domain.
- Reduce the need to revisit setup notes later.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bouncer to Notis once.
- 2Tell Notis in one plain-language instruction to verify the domain when a domain setup page is created.
- 3Select Page Created and choose the Notion location and report channel that fit your domain notes.
- 4Add one real test domain and review the Bouncer result.
Questions about this workflow
What does Bouncer check?
It verifies domain validity and configuration, including MX records and catch-all behavior.
Does it verify an individual email?
No. This action checks a domain.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bouncer. A trigger fires from one place; an action lands in another.
Notion triggers
Bouncer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Toxicity List Job Status
Tool to check the status of a specific toxicity list job. use after creating a toxicity list job to poll its status until completion.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Batch Request
Tool to initiate a batch email verification request. use when you have multiple emails to verify in one api call. returns a batch id and initial status.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Toxicity List Job
Tool to create a toxicity analysis job for a list of email addresses. use when you need to batch-process toxicity checks for multiple emails at once.
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.
Delete batch request
Tool to delete a batch verification request. use when you need to remove all associated emails and results for a specific batch after confirming that the batch data is no longer required.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Toxicity List Job
Tool to delete a specific toxicity list job. use when you need to remove a completed or unwanted toxicity analysis job after confirming its id.
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.
Finish Batch
Tool to mark a batch verification process as finished. use after batch processing completes to stop further verifications and reclaim unused credits.
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.
Get Batch Results
Tool to retrieve the results of a batch verification process. use after submitting a batch to fetch all processed email verification outcomes.
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.
Verify Domain
Tool to verify the validity and configuration of a domain. use when you need to confirm the domain's mx records and catch-all behavior.
Connect any two apps with Notis in the middle.
Notion and Bouncer, 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 Bouncer.