Keep your course catalogue references current
A structural change in your Notion catalogue can prompt a fresh look at the available Membervault products.
Trigger
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.
Action
Get Courses
Tool to retrieve all courses (products) in the membervault account. use when you need to list available courses after setting up authentication.
Why this helps
Course references can become stale after a database schema change, leaving teams unsure which products remain available.
- Prompt a fresh review when catalogue structure changes.
- Reduce the chance that teams rely on stale product references.
- Keep the course list available in a reported automation run.
Setup
Build it in a few focused steps.
- 1Connect Notion and Membervault to Notis once through the portal.
- 2Create an automation prompt to retrieve the current Membervault course list after the course catalogue schema changes.
- 3Select Data Source Schema Updated for the catalogue data source and choose a channel for run reports.
- 4Test with a real schema update and review the returned course list.
Questions about this workflow
Does Get Courses update the Notion database?
No. It retrieves Membervault courses; the team can review the result and update Notion as needed.
Can this detect any schema change?
Yes. Select the schema update trigger for the relevant data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Membervault. A trigger fires from one place; an action lands in another.
Notion triggers
Membervault actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add User to Course
Tool to add a user to a specified product. use when enrolling a user into a course without duplication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete User
Tool to completely delete a user from the account, including all data, progress, and quiz answers (irreversible). use when you need to permanently remove a user. example: "delete user with email user@example.com"
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Courses
Tool to retrieve all courses (products) in the membervault account. use when you need to list available courses after setting up authentication.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Membervault, 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 Membervault.