Skip to content
Notis

Understand the context behind a status change

When a Notion status or priority changes, retrieve related memories to help you decide what follow-up is needed.

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

Perform semantic search on memories

Searches memories semantically using a natural language query (required if `only metadata based search` is false) and/or metadata filters. required: at least one of agent id, user id, app id, or run id must be provided. when `only metadata based search` is true, the `metadata` parameter is required.

Why this helps

A change can signal a new commitment or blocker, but the history needed to respond may be elsewhere.

  • Review relevant history when a status changes.
  • Make follow-up decisions with more context.
  • Reduce the chance of missing a related commitment.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Mem0 to Notis once in the portal.
  • 2Create an automation through the portal or by describing the status review to Notis.
  • 3Prompt Notis to search Mem0 for context related to meaningful Notion status or priority changes.
  • 4Select the Notion Page Properties Updated trigger and choose a channel for run reports.
  • 5Test with one real status change and verify the Mem0 search has a valid entity association.

Questions about this workflow

Can the search ignore routine property changes?

Describe meaningful status or priority changes in the prompt and ask Notis to skip routine updates.

What does Mem0 return?

The semantic search returns memories relevant to the query and required entity association.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Mem0 actions

Recurring trigger

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

TriggerScheduled

Add member to project

Adds an existing user to a project (identified by `project id` within organization `org id`), assigning a valid system role.

ActionInstant

Webhook trigger

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

TriggerInstant

Add new memory records

Stores new memory records from a list of messages, optionally inferring structured content; requires association via `agent id`, `user id`, `app id`, or `run id`.

ActionInstant

All Page Events

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

TriggerPolling

Add organization member

Adds a new member, who must be a registered user, to an organization, assigning them a specific role.

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

Create a new agent

Creates a new agent with a unique `agent id` and an optional `name`; additional metadata may be assigned by the system.

ActionInstant

New Comment

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

TriggerPolling

Create a new agent run

Creates a new agent run in the mem0.ai system.

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

Create a new application

Creates a new application, allowing metadata to be passed in the request body (not an explicit field in this action's request model); ensure `app id` is unique to avoid potential errors or unintended updates.

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

Create a new organization entry

Creates a new organization entry using the provided name and returns its details.

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

Create a new user

Creates a new user with the specified unique `user id` and supports associating `metadata` (not part of the request schema fields).

ActionInstant

Connect any two apps with Notis in the middle.

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