Connect a documented email process to Kit events
Document a new event-notification need in Notion and let Notis create the corresponding Kit webhook after the destination and event are confirmed.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Create Webhook
Tool to create a new webhook subscription. use when you need subscriber or purchase event notifications.
Why this helps
A documented need for event notifications can remain a manual setup item that gets lost among other process changes.
- Make an approved notification setup request actionable.
- Reduce the gap between process documentation and event delivery setup.
- Keep webhook setup tied to a clear operational decision.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kit to Notis once through the portal.
- 2Confirm the approved webhook purpose, destination details, and supported Kit event before creating the automation.
- 3Create an automation in the portal or describe the qualifying Notion update to Notis in plain language.
- 4Select Notion Page Updated for the process page and choose a channel for run reports.
- 5Test the approved request and verify the webhook exists in Kit.
Questions about this workflow
Will any process page update create a webhook?
Your prompt should require an explicit, approved request and the necessary webhook details. Avoid triggering creation from ordinary edits.
What kinds of events does the Kit action support?
The action is for subscriber or purchase event notifications. Confirm the intended event and destination details first.
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.