Revisit transactional messages when customer flows change
When a flow changes in Notion, let Notis fetch your transactional templates so you can check that essential messages still fit the customer journey.
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
List Transactional Messages
Tool to list all transactional message templates. use when you need to fetch available transactional messages.
Why this helps
Transactional content can get out of step with a customer flow when documentation and messaging are maintained separately.
- Connect flow documentation changes to a messaging review.
- Make the current transactional template list easier to retrieve.
- Reduce the chance of overlooking key customer communications during a change.
Setup
Build it in a few focused steps.
- 1Connect Notion and Customer.io to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to review transactional templates after flow changes.
- 3Describe which Notion customer-flow updates should prompt Notis to retrieve Customer.io transactional messages.
- 4Select the Notion Page Properties Updated trigger, choose a channel for run reports, and test with one real flow update.
Questions about this workflow
Does this change or send transactional messages?
No. It retrieves the available templates so you can review them.
Which Notion updates should matter?
Use one plain-language instruction to describe the customer-flow updates that should prompt a review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Customerio. A trigger fires from one place; an action lands in another.
Notion triggers
Customerio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Suppress Customer Profile
Tool to suppress a person. use when you need to permanently delete a customer's profile and prevent them from being re-added.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Integrations
Tool to retrieve a list of integrations in your workspace. use when you need to discover configured integrations.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Messages
Tool to retrieve a list of messages sent from your workspace. use when you need paginated delivery metrics for messages, e.g., list email messages delivered between two timestamps.
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.
Get Segment Details
Tool to retrieve details of a specific segment. use after identifying the segment id from list segments.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Segment Membership
Tool to retrieve people in a specific segment. use when you need to page through segment membership after identifying segment id.
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.
Get Segments
Tool to retrieve a list of segments in your workspace. use when you need to fetch all segments after configuring segment rules.
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.
Get Trigger
Tool to retrieve details about a specific trigger. use after triggering a broadcast to confirm its status and metadata.
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 Triggers
Tool to retrieve a list of triggers for a specific broadcast. use after identifying broadcast id to inspect associated triggers.
Connect any two apps with Notis in the middle.
Notion and Customerio, 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 Customerio.