Carry recorded double opt-in consent into Mailcoach
Record the completed opt-in in Notion and let Notis confirm the matching Mailcoach subscriber.
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
Confirm Subscriber
Tool to confirm a subscriber’s subscription. use when finalizing the double opt-in process after they have provided subscriber details. example: "confirm subscriber with uuid 123e4567-e89b-12d3-a456-426614174000"
Why this helps
A completed confirmation can sit waiting while someone remembers to update the email platform.
- Reduce manual steps after confirmation is recorded.
- Keep consent tracking and subscriber status aligned.
- Avoid leaving an eligible subscriber in limbo.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailcoach to Notis once through the portal.
- 2Create an automation with Page Properties Updated for the opt-in tracking data source.
- 3Write one plain-language instruction to confirm a matching subscriber only after Notion records completed double opt-in.
- 4Choose a channel for run reports and test with one real confirmed consent record.
Questions about this workflow
Should this confirm every new subscriber?
No. Limit the prompt to records that clearly indicate completed double opt-in consent.
What if the subscriber cannot be matched?
Tell Notis to report the missing or uncertain match for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailcoach. A trigger fires from one place; an action lands in another.
Notion triggers
Mailcoach actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Mailcoach Campaign
Tool to create a new mailcoach campaign. use when you need to send or schedule an email campaign to a specific list or segment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Email List
Tool to create a new email list. use when you need to manage and organize subscribers before sending campaigns. use after authentication.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add suppression
Tool to add a suppression entry. use after detecting a bounce, spam complaint, or manual block.
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.
Add Tag to Email List
Tool to create a new tag within a specific email list. use after confirming the email list exists.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add Tags to Subscriber
Tool to add tags to a subscriber. use after retrieving a subscriber's uuid to segment them.
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.
Add Template
Tool to create a new email template. use after preparing template name and optional html content.
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.
Add Transactional Email Template
Tool to create a new template that can be used for transactional emails.
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.
Append to Subscriber Import
Tool to append csv data to an existing subscriber import. use after retrieving a subscriber import when additional subscriber data needs to be added.
Connect any two apps with Notis in the middle.
Notion and Mailcoach, 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 Mailcoach.