Keep useful Notion views understandable
Capture the purpose and context of new Notion views to make workspace organization easier to remember.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
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
A view can be created to solve a specific workflow need, but that reason may be forgotten once attention shifts.
- Recall why a view was set up.
- Keep useful workspace conventions easier to understand.
- Avoid recreating views because their original purpose is unclear.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mem0 to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to set one up conversationally.
- 3Prompt Notis to save the available purpose and context of each new Notion view as a Mem0 memory.
- 4Select the Notion View Created trigger and choose a channel for run reports.
- 5Test with one real view creation and confirm the saved context is accurate.
Questions about this workflow
Which view types can trigger this?
The event can include table, board, gallery, calendar, list, timeline, or gantt views.
Does the event always include why the view was made?
Not necessarily. Ask Notis to preserve the purpose when available and avoid guessing.
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.