Review index structure when your Notion schema changes
When columns change, quickly inspect the related index mapping and decide whether its structure still fits your workflow.
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 Index Schema
Tool to get the complete schema/mapping of a specific elasticsearch index. use when you need to understand the structure, field types, and mappings of an index.
Why this helps
Schema changes can create uncertainty about whether the index still reflects the information the team expects to find.
- Make index structure easier to review after schema changes.
- Catch possible data-model drift sooner.
- Avoid searching for mapping details manually.
Setup
Build it in a few focused steps.
- 1Connect Notion and Elasticsearch to Notis once in the portal.
- 2Ask Notis to retrieve the relevant Elasticsearch index schema after a Notion data source schema update and summarize fields for review.
- 3Choose the Data Source Schema Updated trigger and select a reporting channel.
- 4Test with a real schema change and verify the mapping summary.
Questions about this workflow
Does this change the Elasticsearch mapping?
No. Get Index Schema reads the mapping so you can review it.
Can it tell which Notion property changed?
The Notion event includes updated property details that can inform the review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Elasticsearch. A trigger fires from one place; an action lands in another.
Notion triggers
Elasticsearch actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Index Schema
Tool to get the complete schema/mapping of a specific elasticsearch index. use when you need to understand the structure, field types, and mappings of an index.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Indices
Tool to list all available elasticsearch indices. use when you need to get a list of indices in your elasticsearch cluster, optionally filtering by pattern, health status, or other criteria.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Query Index
Tool to query an elasticsearch index with various filters, time ranges, and pagination support. use when you need to search for documents in an index with complex filtering criteria.
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 Elasticsearch, 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 Elasticsearch.