Turn an enrollment approval request into Memberspot access
An external approval can reach Notis as a webhook and prompt the corresponding Memberspot offer update, so the access step is less likely to be missed.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Set user offer state
Tool to revoke or set the state of a specific offer for a user. use after confirming whether the user should gain or lose access.
Why this helps
Approvals made in a separate enrollment tool can leave a gap before the learner's Memberspot offer is updated.
- Connect an external approval signal to course access follow-up.
- Reduce repeated entry of an approved decision.
- Use the prompt to keep offer and approval rules clear.
Setup
Build it in a few focused steps.
- 1Connect Notion and Memberspot to Notis once through the portal if you also need Notion learner context.
- 2Create an automation in the portal or ask Notis to handle the enrollment system's incoming approval request.
- 3Write one plain-language instruction describing how the request identifies the learner and which Memberspot offer state the approval means.
- 4Select an incoming webhook trigger, choose a channel for run reports, and test with one real approval request.
Questions about this workflow
Does the webhook come from Notion?
This workflow uses a Notis-native webhook trigger for an external tool or custom backend. Notion can still provide context if connected and referenced in your prompt.
Can the workflow activate any arbitrary offer?
Use a specific offer and state described in your prompt, and test with an approval that should receive that access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Memberspot. A trigger fires from one place; an action lands in another.
Notion triggers
Memberspot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Login Token
Tool to generate a one-hour login token for a user. use when you need to auto-login a user by their uid (token expires after one hour).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Users
Tool to delete one or more users from the platform. use when you need to remove specified users by their email addresses. only existing school users are removed; invalid or out-of-school emails are ignored.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Find user by email
Tool to retrieve a user's details by their email address. use when you need to look up a user after obtaining their email.
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 custom user properties
Tool to list all defined custom user properties. use when you need to retrieve metadata of custom user properties after authentication.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List all offers
Tool to retrieve a list of all offers. use after authentication to fetch available offers.
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.
List Users
Tool to list all users. use when you need to fetch users with optional filtering and pagination.
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.
Set order state
Tool to set the state of an order-based offer for a user. use when you need to activate, deactivate, or remove an offer based on its order id.
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.
Set user offer state
Tool to revoke or set the state of a specific offer for a user. use after confirming whether the user should gain or lose access.
Connect any two apps with Notis in the middle.
Notion and Memberspot, 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 Memberspot.