Turn a Notion audience request into a MailerLite group
When someone leaves an audience setup request in Notion, let Notis create the corresponding MailerLite group and keep the work moving.
Trigger
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.
Action
Create Group
Tool to create a new subscriber group. use after deciding the group name for categorization.
Why this helps
Requests tucked into comments can be hard to notice again once you have switched to other work.
- Give actionable audience requests a concrete outcome.
- Reduce the need to revisit comment threads manually.
- Keep coordination work from getting buried.
Setup
Build it in a few focused steps.
- 1Connect Notion and MailerLite to Notis once, and ensure the Notion connection has comment access.
- 2Create an automation asking Notis to create a MailerLite group when a comment requests a new audience group.
- 3Select Comment Created and scope it to the relevant page if appropriate.
- 4Choose a channel for run reports.
- 5Test with one real, clearly worded group request comment.
Questions about this workflow
What access does Notion comment triggering require?
The Notion integration needs the Read comments capability. A connection authorized before enabling it may need to be re-authorized.
Should every comment create a group?
No. The prompt should describe the specific kind of request that merits creating a group.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailerlite. A trigger fires from one place; an action lands in another.
Notion triggers
Mailerlite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create automation
Create automation
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create/Update E-commerce Customer
Tool to create or update a customer record for a shop. use when syncing shop customers or onboarding new purchases.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create E-commerce Shop
Tool to connect a new e-commerce shop. use when you need to integrate a store for automations, product imports, and sales tracking.
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.
Create Field
Tool to create a new custom field. use when distinct subscriber attributes are needed before assigning or updating subscriber data. call once per field key.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Group
Tool to create a new subscriber group. use after deciding the group name for categorization.
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.
Create Segment
Tool to create a new subscriber segment. use when grouping subscribers by custom criteria before sending targeted campaigns.
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.
Create Webhook
Tool to register a new webhook url for specified event types. use when you need real-time notifications for selected mailerlite events.
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.
Delete Automation
Tool to delete an automation workflow by id. use when you need to remove an automation after confirming it's no longer needed. returns success=true on 204 no content.
Connect any two apps with Notis in the middle.
Notion and Mailerlite, 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 Mailerlite.