Move a product announcement from plan to customer inbox
When the launch page is ready, ask Notis to trigger the prepared Customer.io announcement broadcast and keep the handoff in one place.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Trigger Broadcast
Tool to manually trigger a broadcast. use when you need to override the default audience and provide personalization data after confirming the broadcast id.
Why this helps
A launch plan can be complete while the announcement still waits in another tool for someone to remember it.
- Connect the launch planning moment to customer communication.
- Reduce the gap between recording a release and announcing it.
- Give launches a repeatable announcement routine.
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 handle launch announcements in plain language.
- 3In one instruction, describe which new Notion launch pages should trigger the prepared Customer.io broadcast.
- 4Select the Notion Page Created trigger, choose a channel for run reports, and test with one real launch page.
Questions about this workflow
Can the workflow draft a Customer.io campaign?
No. It triggers a broadcast that you have already prepared in Customer.io.
Can this be limited to launch pages?
Describe the relevant launch pages in the plain-language instruction and use a suitable Notion trigger scope when creating the automation.
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.