Turn Notion support issues into Insighto intents
Capture each newly documented support gap as an Insighto intent, so customer questions are easier to handle consistently.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Intent
Tool to create a new intent in insighto.ai. use when adding custom intents before training or deployment. call after confirming intent attributes.
Why this helps
Repeated customer questions can stay buried in a task database until someone remembers to turn them into chatbot coverage.
- Convert documented support gaps into chatbot-ready intent candidates.
- Reduce the mental load of carrying unresolved customer questions.
- Keep intent creation tied to the team's existing Notion workflow.
Setup
Build it in a few focused steps.
- 1Connect Notion and Insighto ai to Notis once in the portal.
- 2Create an automation in the portal or tell Notis what outcome you want in plain language.
- 3Instruct Notis to create an Insighto intent from each new Notion support issue, using its documented question and resolution context.
- 4Select the Notion New Page trigger for the relevant database and choose a channel for run reports.
- 5Test with one real support issue and confirm the intent appears in Insighto.
Questions about this workflow
Does this create an intent for every new database page?
The prompt can tell Notis which new pages represent support issues and which details to use. Test with a real example to confirm the intended records are handled.
Does the workflow train or deploy the intent?
No. The available Insighto action creates an intent. Training or deployment is a separate step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Insighto ai. A trigger fires from one place; an action lands in another.
Notion triggers
Insighto ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Intent
Tool to create a new intent in insighto.ai. use when adding custom intents before training or deployment. call after confirming intent attributes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Provider
Tool to create a new provider. use after obtaining org id to register the provider.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Widget
Tool to create a new widget with specified attributes. use after confirming assistant id and widget type.
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 Contact By ID
Tool to retrieve details of a specific contact by contact id. use when you have a valid contact id and need the full contact profile.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get List Of Contacts
Tool to fetch a paginated list of contacts. use after confirming a valid api key to iterate through pages of contacts.
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.
Get List Of Conversations
Tool to fetch a list of conversations. use after specifying date range and filters to retrieve conversation metadata.
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.
Get List Of Datasources
Tool to list all existing data sources. use when you need to fetch the complete set of data sources.
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.
Read Contact Custom Field List
Tool to retrieve a list of custom fields associated with contacts. use when you need to inspect or sync contact metadata definitions.
Connect any two apps with Notis in the middle.
Notion and Insighto 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 Insighto ai.