Verify a test email when you create a database
When you create a database for contact work, let Notis verify a known test address as a small setup checkpoint.
Trigger
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.
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
New workspace structures can be ready to use before anyone has checked that the related contact workflow is sound.
- Add an email check to a database setup milestone.
- Use one known address to validate your setup routine.
- Keep a new contact workflow from feeling unfinished.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kickbox to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis to verify a designated test email when a new contact-related database is created.
- 3Select Notion Database Created as the trigger and choose where run reports should appear.
- 4Test the automation with a real contact database setup and designated test address.
Questions about this workflow
What does this database trigger represent?
It fires when a Notion database container is created. A data source added to an existing database is a separate event.
Should this check a real prospect?
Use a designated test contact for this setup-focused workflow, and tell Notis to skip the check if that test address is unavailable.
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.