Know your verification credits before starting a batch
Mark a batch ready in Notion and have Notis check your remaining Listclean credits before you commit to verification.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get Remaining Credits
Tool to retrieve remaining verification credits. use when you need to check your available account credits before performing more email verifications.
Why this helps
Starting a batch without knowing the available credits can create a frustrating stop in the middle of focused work.
- Check capacity at a useful decision point.
- Avoid an unexpected interruption after starting batch work.
- Keep the next step visible in your chosen run-report channel.
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 retrieve remaining Listclean credits when an email batch is marked ready and report the balance.
- 4Select the Notion Page Properties Updated trigger and choose a channel for run reports.
- 5Update one real test batch to ready and review the reported balance.
Questions about this workflow
Does the credit check run verification?
No. It retrieves the remaining Listclean verification credits so you can decide what to do next.
Can it run for a particular database?
Scope the page-properties trigger to the relevant data source when setting it up.
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.