Give new Notion comments their own thread
Keep comment-driven follow-up grouped in a fresh conversation instead of losing it in a busy workspace.
Trigger
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.
Action
Create Thread
Tool to create a new conversation thread. use when starting a fresh chat session or grouping messages into a distinct thread.
Why this helps
Useful requests in comments can disappear among page edits and unrelated conversations.
- Start a distinct conversation for a new comment.
- Make comment follow-up easier to keep together.
- Reduce the chance that a request gets buried in workspace activity.
Setup
Build it in a few focused steps.
- 1Connect Notion and Langbase to Notis once through the portal.
- 2Create an automation and describe the comment-to-thread outcome in one prompt.
- 3Pick the Notion Comment Created trigger and choose a channel for run reports.
- 4Test with one real comment and confirm a new Langbase thread is created.
Questions about this workflow
Does it monitor all comments?
The workspace-wide Comment Created trigger fires for comments the integration can access, subject to its comment capability.
What does the Langbase action create?
It creates a new conversation thread; it does not write a reply to Notion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Langbase. A trigger fires from one place; an action lands in another.
Notion triggers
Langbase actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Split Content into Chunks
Tool to split content into smaller chunks. use when processing large text segments to fit downstream limits.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Thread
Tool to create a new conversation thread. use when starting a fresh chat session or grouping messages into a distinct thread.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Documents in Memory
Tool to list documents in a specific memory. use when you need to fetch document metadata (and optionally vectors) from a memory after confirming its name. supports pagination via limit and startafter parameters.
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.
Get Thread Details
Tool to retrieve details of a specific conversation thread. use when you need the full thread details by its id after confirming its existence.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Thread Messages
Tool to list all messages in a conversation thread. use after obtaining the thread id to fetch its messages.
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.
Create Memory
Tool to create a new memory. use when storing a new memory record in langbase after confirming memory details.
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 Memory
Tool to delete a specific memory. use when you need to permanently remove a stored memory by its name.
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 Memories
Tool to list all memory objects. use when you need to fetch stored memories for context retrieval.
Connect any two apps with Notis in the middle.
Notion and Langbase, 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 Langbase.