Carry useful Notion member note changes into Memberstack
Let Notis update the relevant member detail when a useful note changes, reducing the repeated work of keeping profiles current.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Update Member
Tool to update an existing member's information. use when you have a member id and need to modify their email, customfields, metadata, json data, or loginredirect.
Why this helps
Important member context can become outdated when a Notion note is maintained but the application profile is left behind.
- Keep selected member details aligned across tools.
- Avoid repeating small profile updates by hand.
- Report notes that need a clearer member match.
Setup
Build it in a few focused steps.
- 1Connect Notion and Memberstack to Notis once through the portal.
- 2Create an automation with an instruction to update the relevant Memberstack profile detail when a qualifying member note changes.
- 3Select Page Content Updated for the member-notes data source and pick a channel for run reports.
- 4Test with one real note and verify the intended profile detail.
Questions about this workflow
Will this copy every note into the profile?
Describe only the specific detail you intend to update and use a scoped trigger for the relevant notes.
Can it update metadata or custom fields?
The Update Member action supports custom fields and metadata; name the intended information in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Memberstack. A trigger fires from one place; an action lands in another.
Notion triggers
Memberstack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Member
Tool to create a new member in your application. use after gathering email, password, optional plans, custom fields, metadata, and redirect.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Member
Tool to permanently delete a member from your application. use after confirming you no longer need the member's data and have the member id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Member
Tool to retrieve a specific member by id or email. use when you need to fetch member profile details for a given identifier (id or email). example: "get member mem sb 12345".
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.
List Members
Tool to retrieve a paginated list of all members in your application. use when you need to iterate through members with cursor-based pagination.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Plans
Tool to list all available membership plans. use when you need to retrieve plan ids and details before assigning or comparing plans.
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.
Remove Free Plan
Tool to remove a free plan from an existing member. use after confirming the member's subscription status. example: "remove free plan pln sb 67890 from member mem sb 12345".
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.
Update Member
Tool to update an existing member's information. use when you have a member id and need to modify their email, customfields, metadata, json data, or loginredirect.
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 Memberstack, 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 Memberstack.