Check contact emails raised in discussion
If a contact's email comes up in a discussion, let Notis handle the verification so the follow-up does not depend on memory.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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
A contact decision discussed on a page can be separated from the later task of validating the address.
- Keep verification connected to a chosen contact discussion.
- Reduce the chance that a discussed address is overlooked.
- Avoid a separate task just to initiate a check.
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 contact emails mentioned in new comments on the chosen page or block.
- 3Select Notion New Comment as the trigger, specify the intended page or block in the prompt, and choose a run-report channel.
- 4Test by adding one real comment with an email address to that page or block.
Questions about this workflow
How does this differ from a workspace comment trigger?
This trigger is for comments on a specified Notion block or page, while the workspace-wide comment event can cover any accessible comment.
Does Notis need comment access?
Yes. The Notion integration needs permission to read comments for comment events to flow.
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.