Close the loop when a milestone is done
Let a completed milestone create a small, useful cue to record progress and focus on what comes next.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Send SMS
Tool to send sms messages. use when you need to dispatch one or multiple messages after gathering user details.
Why this helps
Founders often move straight to the next task without noticing or communicating meaningful progress.
- Make meaningful progress visible at completion.
- Prompt a clean handoff to the next task.
- Reduce mental effort spent checking whether a milestone is done.
Setup
Build it in a few focused steps.
- 1Connect Notion and Msg91 to Notis once.
- 2Create an automation in the portal or ask Notis to create it.
- 3Tell Notis in one plain-language instruction to text you when a designated milestone changes to complete, with the milestone name and next step if known.
- 4Pick Notion Page Properties Updated and choose the run-report channel.
- 5Complete one real test milestone and confirm the SMS is concise and useful.
Questions about this workflow
Can I avoid a text for every completed task?
Describe the specific milestone database or type of work that should qualify in your instruction.
Can the message suggest the next step?
Ask Notis to include a known next step when the Notion content provides one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Msg91. A trigger fires from one place; an action lands in another.
Notion triggers
Msg91 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create User Events
Tool to create user events in msg91 segmento. use when you need to record user actions and behaviors.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Event Types
Tool to retrieve all available event types in segmento. use when you need to list recorded event types after authenticating.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Failed Events
Tool to retrieve failed segmento events. use when needing to inspect validation failures for a campaign after execution.
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 Campaigns
Tool to list all campaigns in segmento. use when you need to retrieve campaigns with pagination support.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Send SMS
Tool to send sms messages. use when you need to dispatch one or multiple messages after gathering user details.
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 Msg91, 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 Msg91.