Skip to content
Notis

Keep edited Notion content current in search

Page content changes can prompt a targeted refresh, without another reminder on your task list.

Trigger

Page Content Updated

Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).

Action

Partial Update Objects

Tool to partially update multiple records in the specified index. use when you need to change only selected fields of many objects without replacing entire records. use after confirming objectids and desired updates.

Why this helps

A corrected or expanded page may be fixed in Notion while its searchable version remains stale.

  • Reflect content revisions in search.
  • Reduce reindexing follow-up work.
  • Help teammates find the corrected information.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Algolia to Notis once.
  • 2Create an automation through the portal or by telling Notis what it should do.
  • 3Write one plain-language instruction describing how edited page content should refresh its Algolia record.
  • 4Choose Page Content Updated and select a run-report channel.
  • 5Edit one test page and verify the matching record is current.

Questions about this workflow

Does Notion send every keystroke?

Notion aggregates content edits within a short window, so the trigger is intended for page content updates rather than each keystroke.

Can I scope it to a part of my workspace?

The trigger supports optional page or data source scope; choose the relevant scope when setting up the trigger.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Algolia. A trigger fires from one place; an action lands in another.

Notion triggers

Algolia actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add AB Test

Tool to create an ab test comparing search performance between two variants. use to test different index configurations or search parameters and measure impact on click-through and conversion rates.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Browse Algolia Index

Tool to retrieve all records from an index. use when you need to export or iterate through an entire index dataset.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Clear Objects

Tool to clear records of an index without affecting settings. use when you need to completely wipe all objects (e.g., after a bulk reindex) while preserving index configuration.

ActionInstant

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.

TriggerInstant

Clear Rules

Tool to delete all rules in an index. use when you need to wipe all rules before re-creating them. use after confirming no critical rules require retention.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Clicked Object IDs

Tool to send a click event to algolia to capture clicked items. use immediately after a user click outside of search contexts to report click events.

ActionInstant

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.

TriggerInstant

Clicked Object IDs After Search

Tool to send a click event after a search response. use when you want to report which items a user clicked in search results.

ActionInstant

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.

TriggerInstant

Converted Object IDs

Tool to send a conversion event for items outside of search context. use when tracking conversions on category pages or external flows unrelated to algolia search.

ActionInstant

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.

TriggerInstant

Copy Index

Tool to copy the specified index to a new index. use when you need to duplicate an existing index including records, settings, synonyms, and rules after confirming source and destination names.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Algolia, 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 Algolia.