Keep new subpage context connected
Preserve the key purpose and durable details of new Notion subpages in Mem0 as they are added beneath a parent page.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
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`.
Why this helps
New subpages can scatter related information across a workspace and make it harder to retain the thread.
- Keep useful context from new subpages available for recall.
- Reduce the effort of remembering where supporting details live.
- Retain a clear thread across related pages.
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 ask Notis for this outcome.
- 3Write one prompt asking Notis to save the subpage's purpose and durable context as a Mem0 memory.
- 4Select the Notion Page Added to Page trigger and choose a channel for run reports.
- 5Test by adding one real subpage with useful project context.
Questions about this workflow
Which subpages trigger this workflow?
This trigger fires when a child page is added under the specified parent Notion page.
What information should be saved?
The prompt can ask Notis to preserve the subpage's purpose and lasting context rather than duplicate the full page.
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.
Add member to project
Adds an existing user to a project (identified by `project id` within organization `org id`), assigning a valid system role.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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`.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add organization member
Adds a new member, who must be a registered user, to an organization, assigning them a specific role.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create a new agent run
Creates a new agent run in the mem0.ai system.
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.
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.
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.
Create a new organization entry
Creates a new organization entry using the provided name and returns its details.
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.
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).
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.