Skip to content
Notis

Check contact emails when details change

When you update a contact in Notion, have Notis recheck the address so your next message starts with current information.

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

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

Contact details can change quietly, leaving the address you plan to use out of date.

  • Recheck an address after a contact record is edited.
  • Reduce uncertainty before sending a follow-up.
  • Keep contact maintenance close to your Notion workflow.

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 contact's email with Kickbox whenever a contact record is updated.
  • 3Select Notion Page Properties Updated as the trigger and choose a channel for run reports.
  • 4Test by updating one real contact record with an email address.

Questions about this workflow

Does every page edit trigger this?

This trigger responds to property updates. Ask Notis in the prompt to focus on the contact's email and relevant contact records.

Can I use it for an address I have corrected?

Yes. When the contact record's properties are updated, Notis can use the latest email shown in the page context for 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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.