Connect follow-up status changes with sent-email checks
Change a follow-up record in Notion and have Notis check recent MailerSend sends, making it easier to confirm progress before moving on.
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
Get sent messages
Tool to retrieve a paginated list of sent messages. use after sending emails to view message logs.
Why this helps
A follow-up status can change without making it clear whether an email was sent, leaving the next step uncertain.
- Use a follow-up update as a cue to check sending activity.
- Make progress reviews more grounded in actual email history.
- Reduce uncertainty before picking up the next action.
Setup
Build it in a few focused steps.
- 1Connect Notion and MailerSend to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in a connected channel to create it.
- 3Give Notis one plain-language instruction to retrieve relevant MailerSend sent messages when a follow-up record's properties change.
- 4Select the Notion Page Properties Updated trigger and choose a run-report channel.
- 5Test by updating one real follow-up record and reviewing the returned send history.
Questions about this workflow
Does it update the Notion follow-up record?
No. It retrieves MailerSend messages to support your review.
Can it run on a database record update?
Yes. Page Properties Updated can be scoped to a Notion data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailersend. A trigger fires from one place; an action lands in another.
Notion triggers
Mailersend actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Sending Domain
Tool to add a new sending domain to mailersend. use when you need to register and configure a domain before sending emails.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create SMTP User
Tool to create a new smtp user. use after domain setup to obtain smtp credentials.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create API Token
Tool to create a new api token. use when you need to generate a token with specific permissions in mailersend.
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 Webhook
Tool to create a new webhook for a mailersend domain. use after you have a domain id and need to receive event notifications like sent, delivered, opened, etc.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Webhook
Tool to delete an existing webhook. use when the webhook is no longer needed. returns empty response on successful deletion (http 204).
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 API Quota
Tool to retrieve current api usage quota. use when monitoring api rate limits to avoid exceeding allowed calls.
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 Domain
Tool to fetch information for a specific sending domain. use when you need to verify domain status and dns configuration after setup or changes.
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 Domain Recipients
Tool to list recipients for a domain. use after obtaining the domain id to view recipients with optional pagination.
Connect any two apps with Notis in the middle.
Notion and Mailersend, 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 Mailersend.