Keep a key page's latest context close
When a page changes, make its important new context easier to retrieve.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Create Note
Tool to create a new note in mem. use when you have note content and optional metadata ready to be saved. supports idempotent creation via memid.
Why this helps
A central reference page can change between visits, leaving you unsure what needs attention now.
- Keep an updated reference note in Mem.
- Find changes without rereading an entire page.
- Reduce mental load when returning to a topic.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mem to Notis once through the portal.
- 2Create an automation and instruct Notis in one plain-language prompt to save meaningful new context from the chosen page as a Mem note.
- 3Choose Page Updated and select the page to watch.
- 4Choose a reporting channel and test with one real page change.
Questions about this workflow
What does Page Updated watch?
It fires when a block within the specified Notion page is updated.
Can I watch a page without monitoring the whole workspace?
Yes. Specify the page for the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mem. A trigger fires from one place; an action lands in another.
Notion triggers
Mem actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Collection
Tool to create a new collection in mem. use when you want to group related notes into a dedicated collection after confirming the title.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Note
Tool to create a new note in mem. use when you have note content and optional metadata ready to be saved. supports idempotent creation via memid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Collection
Tool to delete a mem collection. use after confirming the collection id you wish to remove.
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.
Delete Note
Tool to delete a specific note. use when you need to remove a note by its unique identifier after confirming the note id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Read Note
Tool to retrieve the content and metadata of a mem note. use after confirming you have the note's id.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Mem, 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 Mem.