Validate emails as you create contact pages
Capture a contact in Notion and let Notis check the email as part of the same routine.
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
Kickbox Single Verification
Tool to verify a single email address via kickbox. use when you need real-time validation of an individual email before critical workflows.
Why this helps
Address validation often gets postponed when contact capture already involves several small steps.
- Add an email check to contact capture.
- Reduce the gap between recording and validating an address.
- Spend less time revisiting incomplete prospect records.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kickbox to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis to verify the email on each new contact page with Kickbox.
- 3Select Notion Page Created as the trigger and pick where run reports should appear.
- 4Test with one real contact page containing an email.
Questions about this workflow
Will this run for every new page?
The listed trigger can fire for new pages across the workspace. In the prompt, describe the contact pages and email details Notis should act on.
Can Notis use a page's written content?
Describe how to identify the email in the contact page, and Notis can use the page context when carrying out the verification.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kickbox. A trigger fires from one place; an action lands in another.
Notion triggers
Kickbox actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Kickbox Single Verification
Tool to verify a single email address via kickbox. use when you need real-time validation of an individual email before critical workflows.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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 Kickbox, 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 Kickbox.