Create launch audience lists from Notion subpages
Give each product launch its own audience container as soon as its planning page is added under the launch hub.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Create List
Tool to create a new recipient list in Mailercloud for storing and managing contacts. Use when you need to create a new mailing list for organizing contacts.
Why this helps
A new launch page can be ready while the related email audience setup remains on somebody's mental checklist.
- Tie audience setup to the launch planning milestone.
- Reduce hidden follow-up work.
- Keep separate launches easier to organize.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailercloud to Notis once through the portal.
- 2Create an automation with one plain-language prompt to create a Mailercloud list for each qualifying launch subpage.
- 3Select Page Added to Page and choose the Notion launch hub as the parent page.
- 4Choose a channel for run reports and test by adding one real launch subpage.
Questions about this workflow
Does this work for any subpage in the workspace?
Page Added to Page is scoped to a specified parent page, which helps focus it on a launch hub.
Will it fill the list with launch contacts?
No. The listed action only creates the recipient list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailercloud. A trigger fires from one place; an action lands in another.
Notion triggers
Mailercloud actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create List
Tool to create a new recipient list in Mailercloud for storing and managing contacts. Use when you need to create a new mailing list for organizing contacts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create custom property
Create a custom property for contacts in Mailercloud. Custom properties store specific information for contact records. Maximum of 100 properties allowed per account.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Contact Property
Tool to delete a custom contact property by ID. Use when removing unused custom fields from contacts. Cannot delete properties used in webforms.
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 Client Plan
Tool to retrieve client plan information from Mailercloud. Use when you need to check the current subscription status, plan details, or verify API connectivity.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Search Contacts in List
Tool to retrieve contacts in a specific list with pagination. Use when you need to list or search contacts within a known list 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.
Update Contact Property
Tool to update a custom property of contacts in Mailercloud. Use when you need to modify the name or description of an existing custom property. Note: Editing custom property type using this API is not possible - you can only edit the name and description.
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 Mailercloud, 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 Mailercloud.