Skip to content
Notis

Move approved Notion customers into Memberstack

Let a clear approval record start account creation, so the handoff does not depend on remembering another task.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

Create Member

Tool to create a new member in your application. use after gathering email, password, optional plans, custom fields, metadata, and redirect.

Why this helps

An approved customer can wait too long for an account when a founder has to notice the status and repeat the same details elsewhere.

  • Tie account creation to a recorded customer approval.
  • Avoid repeatedly checking an approval list for the next step.
  • Keep incomplete or ambiguous entries visible for follow-up.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Memberstack to Notis once through the portal.
  • 2Create an automation and tell Notis to create a Memberstack member from a new approved customer record only when required account details are present.
  • 3Select New Page for the customer data source and choose where run reports should go.
  • 4Test with one real approved customer record and check the created member.

Questions about this workflow

Can a new page alone prove that a customer is approved?

No. State clearly in the instruction how approval is represented, and only create a member when the entry meets that condition.

Can this assign a paid plan?

The Create Member action supports optional plans, but the instruction should specify an available plan only when that choice is clear and intended.

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.

TriggerScheduled

Create Member

Tool to create a new member in your application. use after gathering email, password, optional plans, custom fields, metadata, and redirect.

ActionInstant

Webhook trigger

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

TriggerInstant

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.

ActionInstant

All Page Events

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

TriggerPolling

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".

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

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.

ActionInstant

New Comment

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

TriggerPolling

List Plans

Tool to list all available membership plans. use when you need to retrieve plan ids and details before assigning or comparing plans.

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

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".

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

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.

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

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.