Keep launch interest organized across Notion and Kit
Capture a person's launch interest in your Notion planning and let Notis label the matching Kit subscriber for later updates.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Tag Subscriber by Email
Tool to associate a subscriber with a tag using an email address. use when you have a tag id and subscriber email ready. use after confirming both resources exist.
Why this helps
Launch interest recorded during planning is easy to forget when it is time to assemble the email audience.
- Collect launch-interest contacts in a recognizable Kit segment.
- Keep planning notes connected to audience preparation.
- Avoid a last-minute manual review of launch leads.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kit to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Describe how a launch page signals explicit interest and identify the existing Kit tag and subscriber match rule.
- 4Select Notion Page Content Updated for the relevant page and choose a run-report channel.
- 5Test by updating one real launch record for a known subscriber.
Questions about this workflow
Will every edit to the launch page tag someone?
The prompt should specify the qualifying content and how Notis identifies the associated subscriber. The trigger itself fires on page content changes.
Does this send a launch email?
No. It applies a Kit tag so you can organize the audience for a later communication.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kit. A trigger fires from one place; an action lands in another.
Notion triggers
Kit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Subscriber to Form
Tool to add a subscriber to a specific form by id. use after confirming form and subscriber ids.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Custom Field
Tool to create a new custom field for subscriber data. use when you need to store extra attributes for subscribers.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Tag
Tool to create a new tag in the account. use when you need a custom label to segment subscribers. use after confirming tag uniqueness to avoid duplicates. example: "create a tag called 'vip' for premium customers."
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.
Create Webhook
Tool to create a new webhook subscription. use when you need subscriber or purchase event notifications.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Broadcast
Tool to delete a specific broadcast. use when you need to permanently remove a broadcast by id (after confirming the id). example prompt: "delete broadcast with id 123"
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.
Delete Custom Field
Tool to delete a specific custom field. use after confirming the custom field id is correct. deletes the field permanently.
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.
Delete Subscriber
Tool to delete (unsubscribe) a subscriber by id. use when you need to remove a subscriber from all sequences and forms after confirming the subscriber exists.
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.
Delete Tag
Tool to delete a tag by id. use when you need to remove obsolete or incorrect tags after confirming the tag exists.
Connect any two apps with Notis in the middle.
Notion and Kit, 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 Kit.