Turn recorded newsletter interest into a subscriber
Keep the interest note in Notion and let Notis handle the Moosend subscriber step.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Add or Update Subscriber
Tool to add or update a subscriber in a mailing list. use after obtaining the mailing list id to manage subscribers.
Why this helps
Newsletter requests recorded in notes or meeting pages are easy to leave behind when attention moves to the next task.
- Keep a captured request from being stranded in a note.
- Reduce context switching between Notion and Moosend.
- Use a prompt to describe when the note represents consent to subscribe.
Setup
Build it in a few focused steps.
- 1Connect Notion and Moosend to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to process newsletter interest recorded in Notion.
- 3Tell Notis in one plain-language instruction to add or update only contacts whose page content clearly records their newsletter request, in your chosen list.
- 4Select Page Content Updated, choose a report channel, and test with one real consented request.
Questions about this workflow
Can I use a meeting note as the source?
Yes. Scope the Page Content Updated trigger to the relevant page or data source, then describe the qualifying request in the instruction.
What should I test?
Use a real contact whose page clearly records a newsletter request and confirm the Moosend subscriber result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Moosend. A trigger fires from one place; an action lands in another.
Notion triggers
Moosend actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add or Update Subscriber
Tool to add or update a subscriber in a mailing list. use after obtaining the mailing list id to manage subscribers.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create custom field
Tool to create a custom field in a mailing list. use when you need to define a new custom field for subscriber data.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Mailing List
Tool to create a new empty mailing list in moosend. use after obtaining api key.
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 Campaign
Tool to delete a campaign. use when you need to permanently remove a draft or sent campaign from your moosend account after confirming its id. deletion is irreversible.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete custom field
Tool to remove a custom field definition from a mailing list. use when you have confirmed the custom field id to delete.
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.
Delete Mailing List
Tool to delete a mailing list. use when you need to permanently remove a mailing list from your moosend account after confirming its id. deletion is irreversible.
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 all campaigns
Tool to retrieve a list of all campaigns in your account. use after acquiring valid api credentials to explore campaign data.
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 All Subscribers
Tool to retrieve subscribers in a specified mailing list by status. use when you need to paginate subscribers after confirming list id and status.
Connect any two apps with Notis in the middle.
Notion and Moosend, 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 Moosend.