Reprioritize with dependency context in view
When priorities shift, surface related indexed records that could change what should happen next.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
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.
Why this helps
Priority updates often happen quickly, while dependencies and older decisions remain buried elsewhere.
- Bring relevant dependencies into a priority review.
- Spot records that may affect sequencing.
- Avoid reopening the same research manually.
Setup
Build it in a few focused steps.
- 1Connect Notion and Elasticsearch to Notis once in the portal.
- 2Ask Notis to query Elasticsearch when a Notion item's properties change and report records that could affect its priority.
- 3Choose the Page Properties Updated trigger for the relevant database and select a reporting channel.
- 4Test by changing one real item's priority and reviewing the returned matches.
Questions about this workflow
Will this change task priority automatically?
No. It surfaces related indexed records for you to consider.
What property updates can trigger it?
The selected Page Properties Updated event fires on property changes in the chosen scope.
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.