Skip to content
Notis

Refresh institution choices when setup tracking changes

When your connection-tracking schema changes, have Notis retrieve available Mx institutions for review.

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

List institutions

Tool to list financial institutions supported by mx. use when you need to retrieve available institutions with optional filters like name, country code, or products; supports pagination.

Why this helps

Changes to connection requirements can leave institution options buried in a separate lookup flow.

  • Pair structural changes with a fresh institution lookup.
  • Make connection planning easier to resume after schema work.
  • Reduce context switches during setup maintenance.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Mx technologies to Notis once in the portal.
  • 2Create an automation in the portal or by asking Notis conversationally.
  • 3In one instruction, ask Notis to retrieve supported Mx institutions when the specified connection-tracking data source schema changes and summarize useful options.
  • 4Select Notion Data Source Schema Updated as the trigger and choose a channel for run reports.
  • 5Test by making a safe schema change and reviewing the institution list.

Questions about this workflow

Does this trigger on every row update?

No. It responds to a data source schema update such as a column being added, removed, or renamed.

Can institution lookup be narrowed?

Describe any relevant institution, country, or product criteria in the instruction when supported.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Mx technologies. A trigger fires from one place; an action lands in another.

Notion triggers

Mx technologies actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Cancel Partner Account

Tool to cancel (disable) a client account under a partner account. this maps to mx platform api: put /users/{guid} with body {"user": {"is disabled": true, "metadata": "..."}}.

ActionInstant

Webhook trigger

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

TriggerInstant

Create account

Tool to create a manual account for a given user. use when you need to add an external or test account to a user record.

ActionInstant

All Page Events

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

TriggerPolling

Retrieve Audience API Credentials

Tool to retrieve audience api credentials. use when obtaining client id and client secret for audience service authentication before generating an access token. credentials must be created in the partner dashboard (partner administrator → authentication → audience api key). the tool prefers explicitly provided values, then falls back to environment variables.

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

Create member

Tool to create a member and start aggregating specified financial products. use after confirming user guid and gathering connection credentials or oauth details.

ActionInstant

New Comment

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

TriggerPolling

Create Partner Account

Tool to create a new client account under a partner account. use when provisioning a new constant contact client after obtaining api key and jwt authorization.

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

Create Partner Account User SSO

Tool to create a new partner account user with single sign-on enabled. use when adding an sso user under a partner client account with 'sso for all users' enabled.

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

Fetch rewards

Tool to initiate rewards aggregation for a specific member. use after connecting the member to trigger an async rewards job.

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

Get configurable widget URL

Tool to retrieve a configurable widget url for a user. use after determining the user guid.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Mx technologies, 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 Mx technologies.