Keep search vocabulary tidy
A periodic synonym review helps your search language stay understandable as your product grows.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Search Synonyms
Tool to search for synonyms in the specified index. use when you need to retrieve synonyms matching a query or filter by type.
Why this helps
Synonyms can become confusing or outdated as a team changes its language.
- Review terminology at a predictable pace.
- Spot entries that may confuse searchers.
- Reduce forgotten maintenance work.
Setup
Build it in a few focused steps.
- 1Connect Notion and Algolia to Notis once.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one instruction, ask Notis to search synonyms and summarize entries that appear redundant or outdated for review.
- 4Choose a recurring cadence and a channel for run reports.
- 5Review the first summary and verify each suggested synonym before editing.
Questions about this workflow
Will it remove synonyms?
No. Search Synonyms retrieves matching synonyms. Use the report to decide what needs changing.
Can I narrow the audit?
Describe the index or synonym category of interest in the instruction.
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Browse Algolia Index
Tool to retrieve all records from an index. use when you need to export or iterate through an entire index dataset.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.
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.
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.
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.
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.