Connect Notion onboarding readiness to Mailchimp
Track readiness in Notion and let Notis place the matching subscriber into the intended Mailchimp email workflow, helping onboarding continue without a manual handoff.
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
Add subscriber to workflow email
Manually add a subscriber to a workflow, bypassing the default trigger settings. you can also use this endpoint to trigger a series of automated emails in an api 3.0 workflow type.
Why this helps
A new customer can be ready for onboarding communication while the person responsible is focused on delivery or another task.
- Shortens the gap between onboarding readiness and email follow-up.
- Reduces reliance on remembering a second system step.
- Keeps the onboarding signal tied to the record that tracks it.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailchimp to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in plain language to start the sequence.
- 3State the onboarding-ready condition and the Mailchimp workflow that should receive the matching subscriber.
- 4Choose Page Properties Updated, pick a channel for run reports, and test with one real onboarding record.
Questions about this workflow
Does this send a single email or a sequence?
This action adds a subscriber to a workflow email. The sequence behavior depends on the Mailchimp workflow configuration.
Can it skip subscribers who are not ready?
Describe the readiness condition in the prompt and trigger from the relevant Notion property update.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailchimp. A trigger fires from one place; an action lands in another.
Notion triggers
Mailchimp actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add automation
Create a new classic automation in your mailchimp account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add batch webhook
Configure a webhook that will fire whenever any batch request completes processing. you may only have a maximum of 20 batch webhooks.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add campaign
Create a new mailchimp campaign.
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 campaign feedback
Add feedback on a specific campaign.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add campaign folder
Create a new campaign folder.
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 cart
Add a new cart to a store.
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 cart line item
Add a new line item to an existing cart.
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.
Add connected site
Create a new mailchimp connected site.
Connect any two apps with Notis in the middle.
Notion and Mailchimp, 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 Mailchimp.