Carry case resolutions into the conversation
When a documented case reaches a clear resolution, put the useful update back into the conversation that needs it.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Complete Conversation
Tool to send a message to a conversation and receive the bot’s reply. use after retrieving or initiating a conversation id.
Why this helps
Closing out a case in an internal page does not automatically close the loop with the person who raised it.
- Close the loop without relying on a separate reminder.
- Keep the message grounded in the documented resolution.
- Reduce duplicate effort between case notes and customer follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Chatbotkit to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one instruction, ask Notis to detect a clearly documented resolution on the scoped case page, identify its matching Chatbotkit conversation, and send a concise update.
- 4Select the Notion Page Updated trigger for the relevant page and choose a channel for run reports.
- 5Test with one resolved case and verify the conversation match before relying on it.
Questions about this workflow
Can I scope this to one case page?
Yes. The Page Updated trigger applies to blocks within a specified Notion page.
What should happen when the case is not resolved yet?
Tell Notis to send no message unless the page contains a clear resolution.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Chatbotkit. A trigger fires from one place; an action lands in another.
Notion triggers
Chatbotkit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Complete Conversation
Tool to send a message to a conversation and receive the bot’s reply. use after retrieving or initiating a conversation id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Integration
Tool to create a new integration. use when you need to set up a support channel integration for a bot after collecting the integration details.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Skillset
Tool to create a new skillset. use when you need to group multiple skills into a single reusable unit.
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.
List Bots
Tool to retrieve a paginated list of all bots. use when you need to browse or manage multiple bots, and iterate pages via cursor.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List conversation messages
Tool to list messages in a conversation with pagination. use after obtaining a conversation id to fetch messages page by 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.
List Conversations
Tool to retrieve a paginated list of conversations. use when you need to page through conversation history.
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.
List Datasets
Tool to list datasets. use when you need to browse or paginate through available datasets.
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.
List Integrations
Tool to retrieve a list of trigger integrations. use when you need to browse or manage configured trigger integrations and iterate pages via cursor.
Connect any two apps with Notis in the middle.
Notion and Chatbotkit, 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 Chatbotkit.