Turn a comment into an email check
When you leave a clear request on a contact page, Notis can verify the address and report back without another handoff.
Trigger
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.
Action
NeverBounce Single Check
Tool to verify a single email address and gather additional information. use when you need real-time validation at the point of entry.
Why this helps
Small requests buried in comments can become forgotten follow-ups when you switch tasks.
- Convert a written request into a concrete check.
- Reduce the need to reopen a contact later just to remember the task.
- Receive the result in a channel you already monitor.
Setup
Build it in a few focused steps.
- 1Connect Notion and NeverBounce to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one instruction to check the referenced contact email when a comment requests verification.
- 4Select the Notion Comment Created trigger and choose a run-report channel.
- 5Test with a comment on a contact page that clearly requests an email check.
Questions about this workflow
Does this require comment access?
Yes. The Notion integration needs the Read comments capability, and an existing connection may need to be re-authorized after enabling it.
Can I scope comments to one page?
The Comment Created trigger supports an optional page scope when selecting the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Neverbounce. A trigger fires from one place; an action lands in another.
Notion triggers
Neverbounce actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Info
Tool to get account information including credits, job counts, and usage statistics. use when retrieving neverbounce account summary after authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create NeverBounce Bulk Verification Job
Tool to create a new bulk verification job with parsing, sampling, and callback options. use for asynchronous list verification with advanced control.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete NeverBounce Job
Tool to permanently delete a job and its results. use when you need to irreversibly remove a bulk verification job. this delete is irreversible.
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.
Download Job Results (GET)
Tool to download job results as a csv file via get. use after job completion to retrieve segmented or enriched csv output.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Retrieve Job Results
Tool to retrieve paginated results for a completed job, including original data and verification outcomes. use after confirming job completion and when paging through results.
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.
Start NeverBounce Job
Tool to start a parsed job when auto start is disabled. use after creating a job with auto start=false.
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 bulk job status
Tool to get the status and progress of a bulk verification job. use when
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.
NeverBounce Account Info
Tool to get account information including credits, job counts, and usage statistics. use after authenticating to retrieve neverbounce account summary.
Connect any two apps with Notis in the middle.
Notion and Neverbounce, 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 Neverbounce.