Review chatflow details after a Notion schema change
A renamed or removed property can affect how a workflow uses project information. Prompt a Flowise review when the Notion schema changes.
Trigger
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.
Action
Get Single Chatflow
Tool to retrieve a chatflow by its ID. Use when you have a chatflow ID and need its full details.
Why this helps
Structural changes can slip past the people maintaining dependent automations and chatflows.
- Make structural changes visible to the workflow owner.
- Bring relevant chatflow details into the review.
- Help catch integration drift earlier.
Setup
Build it in a few focused steps.
- 1Connect Notion and Flowiseai to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis how to identify chatflows related to the changed data source and retrieve their details for review.
- 4Select Data Source Schema Updated, choose a run-report channel, and test with one real schema change.
Questions about this workflow
Will it run for each existing row affected by a new column?
No. Data Source Schema Updated is the structural-change trigger; it is distinct from the page property updates that adding a column may also cause.
What kind of review does this automate?
It retrieves Flowise chatflow details for the relevant review. The instruction should specify how to identify related chatflows.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Flowiseai. A trigger fires from one place; an action lands in another.
Notion triggers
Flowiseai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clone Chatflow
Tool to clone an existing chatflow. Use when you need to duplicate a chatflow by its ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Chatflow
Tool to create a new chatflow in FlowiseAI. Use when you need to programmatically set up chatflows with custom configuration. Call after preparing the chatflow parameters.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Chatflow
Tool to delete a chatflow by its ID. Use after confirming the chatflow ID is correct.
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.
Delete Chat Messages
Tool to delete chat messages for a specific chatflow. Use when you need to remove messages based on optional filters. Use after confirming the chatflow ID.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Tool By ID
Tool to delete a specific FlowiseAI tool by ID. Use after confirming the tool ID is correct.
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.
Export Chatflow
Tool to export a chatflow by its ID. Use after confirming the chatflow exists.
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 All Chatflows
Tool to retrieve all chatflows. Use when you need to list existing chatflows after authentication.
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.
Get Single Chatflow
Tool to retrieve a chatflow by its ID. Use when you have a chatflow ID and need its full details.
Connect any two apps with Notis in the middle.
Notion and Flowiseai, 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 Flowiseai.