Recheck character references after a Notion schema change
A renamed or added property can reshape how a team tracks references. Use the schema change as a cue to review relevant public character details.
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 Public Character By ID
Tool to retrieve a public character by its id. use when you need to fetch details of a single public character by providing its unique id.
Why this helps
Structural changes can leave people unsure where reference IDs now live, creating extra checking and follow-up.
- Notice structural changes that affect a character-reference workflow.
- Use the updated property details to tell Notis whether a lookup is relevant.
Setup
Build it in a few focused steps.
- 1Connect Notion and Chatfai to Notis once through the portal.
- 2Create an automation with one instruction to review relevant public character IDs when the character-reference data source schema changes.
- 3Select Data Source Schema Updated and scope it to the relevant data source if possible.
- 4Choose a run-report channel, then make a safe test schema change and verify the resulting report.
Questions about this workflow
What changes does this trigger detect?
It fires for data source column additions, removals, or renames, and includes information about updated properties.
Will every schema edit find a character ID?
Not necessarily. The prompt should direct Notis to perform a lookup only when the change is relevant and a usable public character ID is available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Chatfai. A trigger fires from one place; an action lands in another.
Notion triggers
Chatfai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Public Character By ID
Tool to retrieve a public character by its id. use when you need to fetch details of a single public character by providing its unique id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or 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.
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 Chatfai, 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 Chatfai.