Carry qualified demo requests into Mailbluster
Let a qualification update in Notion become a clean handoff for your email follow-up routine.
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
Create MailBluster Lead
Tool to create a new lead in mailbluster. use after gathering the lead's email and optional data.
Why this helps
A promising demo request can be buried among other tasks when qualification and email-list maintenance happen separately.
- Surface qualified requests in your email tool
- Reduce manual review and re-entry
- Keep the qualification decision in Notion
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailbluster to Notis once.
- 2Create an automation or tell Notis to create a Mailbluster lead when a demo request becomes qualified.
- 3Select Page Properties Updated for the request database and pick a channel for run reports.
- 4Test by updating one real request to the qualified state.
Questions about this workflow
Can this run only after qualification?
Describe the qualification condition in the prompt so Notis checks it before creating a lead.
Does the workflow schedule a demo?
No. It creates a Mailbluster lead from the qualified request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailbluster. A trigger fires from one place; an action lands in another.
Notion triggers
Mailbluster actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create MailBluster Lead
Tool to create a new lead in mailbluster. use after gathering the lead's email and optional data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Order
Tool to create a new order in mailbluster.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Product
Tool to create a new product in mailbluster. use when you have all product details ready to add it to your mailbluster catalog.
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.
Delete Order
Tool to delete a specific order. use after confirming the order id to remove an order from mailbluster.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Mailbluster Product
Tool to delete a product. use after confirming product existence.
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 Order
Tool to retrieve details of a specific order. use when you have the order's 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.
Get Product
Tool to retrieve details of a specific product. use when you have a valid product id and need full product information.
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.
List Orders
Tool to list all orders. use when you need to retrieve orders with optional pagination, sorting, or searching after authenticating with mailbluster.
Connect any two apps with Notis in the middle.
Notion and Mailbluster, 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 Mailbluster.