Prepare business email checks as you organize outreach
Create an outreach view in Notion and ask Clearout to check business or work account status for its relevant contacts.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Business Account Verify
Tool to check if an email belongs to a business/work account. Use when validating corporate emails before onboarding.
Why this helps
Reorganizing a pipeline often reveals a verification step that still needs to happen before outreach.
- Turn a new review surface into a cue for contact quality work.
- Reduce repeated setup and follow-up remembering.
- Review business account status as part of outreach preparation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Clearout to Notis once in the portal.
- 2Ask Notis to check business or work account status for the relevant contacts when you create an outreach view.
- 3Select View Created and describe the outreach view context in the instruction.
- 4Choose a channel for run reports and test with a view for a small contact group.
Questions about this workflow
Does creating a view change contact records?
The view creation is the trigger. Clearout checks business account status for relevant contact emails based on the instruction.
Is this useful for every new view?
It fits when creating the view signals a real outreach preparation step; use a view context that makes the intended contacts clear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Clearout. A trigger fires from one place; an action lands in another.
Notion triggers
Clearout actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Autocomplete Company to Domain
Tool to autocomplete company names to probable domains with confidence scores. Use after obtaining a company name or URL to get suggestions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Business Account Verify
Tool to check if an email belongs to a business/work account. Use when validating corporate emails before onboarding.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Catch-All Verify
Tool to check if an email domain is catch-all. Use after confirming email validity.
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 Disposable Email
Tool to check if an email is from a disposable provider. Use after acquiring an email address.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Find Domain MX Records
Tool to retrieve MX records for a domain in priority order. Use when you need to find a domain's mail servers (e.g., for email routing setup).
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.
Fetch Domain WHOIS Information
Tool to fetch WHOIS record for a domain. Use when you need WHOIS data for a 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.
Bulk Email Finder
Tool to upload a CSV or XLSX contacts file for bulk email finding. Use when you need to find emails for a list of contacts in bulk.
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.
Cancel Bulk Email Finder Job
Tool to cancel a running bulk email finder job. Use when you need to stop an in-progress list scan before completion.
Connect any two apps with Notis in the middle.
Notion and Clearout, 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 Clearout.