Keep email category choices in step with Notion
Use schema changes as a cue to review available Enginemailer subcategories.
Trigger
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.
Action
Get Subcategories
Tool to retrieve subcategories for a given category. use when you need to list or choose subcategories after selecting a category.
Why this helps
Category changes can create uncertainty about which email grouping to use in later campaigns.
- Prompts a review when the underlying Notion schema changes.
- Reduces guesswork about available Enginemailer subcategories.
- Keeps category maintenance from becoming an untracked task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Enginemailer to Notis once.
- 2Create an automation prompt to retrieve relevant Enginemailer subcategories when a specified email taxonomy data source changes.
- 3Select Data Source Schema Updated and scope it to that data source.
- 4Choose a run-report channel and test by making one real schema change.
Questions about this workflow
Does this change Enginemailer categories?
No. It retrieves available subcategories so you can review the options.
When should I use this?
Use it when a Notion schema update signals that your email category structure may need review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Enginemailer. A trigger fires from one place; an action lands in another.
Notion triggers
Enginemailer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Export Status V2
Tool to check status of a previously requested csv report export. use after initiating an export to poll for completion.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Campaign
Tool to create a new email campaign. use when you need to configure and schedule a campaign before sending.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Export CSV Report V2
Tool to export a transactional email report as csv. use when you need to initiate an export within a specific date range (max past 60 days).
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.
Get Subcategories
Tool to retrieve subcategories for a given category. use when you need to list or choose subcategories after selecting a category.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Insert Subscriber
Tool to add a new subscriber with optional custom fields. use when registering a user to a specific mailing list after verifying their email.
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.
List Campaign
Tool to retrieve a list of undelivered campaigns. use when you need to fetch campaigns awaiting delivery.
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.
Pause Campaign
Tool to pause a scheduled email campaign. use when you need to halt a campaign before sending to apply updates or adjust schedule.
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.
Send Campaign
Tool to send an email campaign immediately. use when the campaign exists, has at least one recipient, and is not scheduled or already delivered. e.g., 'send campaign 123 now'.
Connect any two apps with Notis in the middle.
Notion and Enginemailer, 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 Enginemailer.