Connect Notion to Mx technologies
When something happens in Notion, Notis takes the next step in Mx technologies. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Mx technologies
Check an account balance from a Notion cash task
When you add a cash check task in Notion, retrieve the selected account's current available balance in Mx.
Pull transactions when a month-end review changes
When a Notion review page's properties change, retrieve Mx transaction history so the review can start with the source data.
Refresh budget context from a Notion planning update
When you update a planning page's body, retrieve the user's Mx budgets to support the next planning decision.
Add Mx goals context to a new Notion goal
When a new Notion goal page is created, retrieve Mx goals to make financial priorities easier to compare.
Retrieve member context from a Notion finance comment
A new finance-page comment can prompt Notis to list Mx members, giving a follow-up discussion clear account context.
Check Mx categories when a Notion comment flags a transaction
When a comment on a specified finance page raises a categorization question, retrieve the user's Mx categories for reference.
Retrieve accounts for a new finance subpage
When a new subpage is added under a finance hub, retrieve the user's Mx accounts for the overview or checklist.
Review budgets when a Notion finance property changes
When a finance page's properties change, retrieve Mx budgets to help keep planned spending aligned with current limits.
Review Mx transaction taggings after a Notion update
When a Notion finance page property changes, retrieve Mx taggings to provide context for a tagging review.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Mx technologies
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.