Make a weekly cash check easier to remember
Let Notis retrieve selected Mx balances each week so your runway review has a reliable starting point.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Read account balance
Tool to retrieve the available balance for a specific account. use after confirming the user and account guids.
Why this helps
A recurring cash check is easy to postpone when it depends on remembering to open several accounts.
- Create a consistent weekly checkpoint for cash visibility.
- Reduce the mental load of remembering a routine lookup.
- Receive balance context where you review your week.
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 ask Notis to set it up conversationally.
- 3Give Notis one instruction to retrieve available balances for selected Mx accounts and summarize them for your weekly Notion runway review.
- 4Choose a weekly schedule, select a channel for run reports, and specify the desired time.
- 5Test once with a real account before relying on the recurring run.
Questions about this workflow
Will Notis write the snapshot into Notion?
This workflow retrieves balances and reports them on the selected channel. Describe any supported follow-up you need in the instruction.
Can this run at a specific weekly time?
Choose the weekly schedule and time when creating the automation.
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.
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": "..."}}.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.
Fetch rewards
Tool to initiate rewards aggregation for a specific member. use after connecting the member to trigger an async rewards job.
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.
Get configurable widget URL
Tool to retrieve a configurable widget url for a user. use after determining the user guid.
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.