Resolve email questions raised in Notion
When a teammate flags an address in a comment, let Notis check it so the discussion can move toward a clear next step.
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
Verify Email Address
Tool to verify an email's validity. use when you need to ensure an address is deliverable and non-disposable, after collecting a user's email.
Why this helps
An email concern buried in a comment can be forgotten while you switch between the discussion and verification tools.
- Respond to address questions while the context is fresh.
- Reduce the need to copy a contact into a separate check.
- Keep a lightweight review step tied to team discussion.
Setup
Build it in a few focused steps.
- 1Connect Notion and Listclean to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Tell Notis to identify the relevant contact email from a new comment and its page context, then verify it with Listclean.
- 4Select the Notion Comment Created trigger and choose a channel for run reports.
- 5Test by commenting on one real contact page with an email-check request.
Questions about this workflow
Can it respond to every comment in my workspace?
This trigger can fire for comments across the workspace the integration can access. Describe the relevant email-check request clearly in the instruction.
What access does the trigger need?
Notion comment events require the integration to have Read comments capability. A connection authorized before that capability was enabled may need reauthorization.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Listclean. A trigger fires from one place; an action lands in another.
Notion triggers
Listclean actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Bulk Verification List
Tool to create a csv file with provided email addresses for bulk verification. use when you need to generate a file for bulk upload through listclean upload list.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Profile
Tool to retrieve the authenticated account's profile. use after obtaining a valid auth token to fetch user account data.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Remaining Credits
Tool to retrieve remaining verification credits. use when you need to check your available account credits before performing more email verifications.
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.
Verify Email Address
Tool to verify an email's validity. use when you need to ensure an address is deliverable and non-disposable, after collecting a user's email.
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 Listclean, 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 Listclean.