Give content discussions their current item context
A comment can raise a question that is hard to answer from the thread alone. Have Notis retrieve the related Kontent.ai item for the run report.
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
Get Content Item
Tool to retrieve a specific content item by its identifier. use after confirming the environment id and item identifier.
Why this helps
Reviewers lose time switching from a comment thread to find the content it refers to.
- Pair a discussion with the item under review.
- Reduce context switching during feedback follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kontent.ai to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for the outcome.
- 3Use one instruction asking Notis to identify the referenced Kontent.ai item from the comment context and retrieve it.
- 4Choose the Notion Comment Created trigger and select a channel for run reports.
- 5Test with one real comment on a content review page.
Questions about this workflow
Does the comment trigger require any extra access?
Notion comment events require the integration's Read comments capability. A connection authorized before that capability was enabled may need reauthorization.
Does it work for every comment?
The workspace-wide Comment Created trigger can fire for comments the integration can access; use a relevant Notion page context in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kontent ai. A trigger fires from one place; an action lands in another.
Notion triggers
Kontent ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Content Item
Tool to retrieve a specific content item by its identifier. use after confirming the environment id and item identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Language
Tool to retrieve a specific language by its id. supports management api directly and delivery api via normalization.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Language Variant
Tool to retrieve a specific language variant of a content item. use after confirming the item and language identifiers when needing localized content.
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 Content Items
Tool to list content items from the delivery api. use when fetching content items for a specified environment, optionally providing a continuation token for pagination.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Content Types
Tool to list content types within a kontent.ai environment. use when you need to retrieve a paginated list of content type definitions. use after confirming the environment id.
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 Languages
Tool to list languages in a kontent.ai project. use when you need to retrieve all languages for a specified environment after confirming the project 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 Kontent ai, 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 Kontent ai.