Email the Team When a New Subpage is Added to a Project
When a new subpage is added under a project in Notion (e.g., a new section or deliverable), the team gets an email--keeping everyone aware of growing scope.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Send Email
Send an email using agentmail api
Why this helps
New subtasks or sections are added to projects but team members don't know, creating silent scope creep and coordination breakdowns.
- Team members discover scope changes immediately
- Reduces silent scope creep and miscommunication
- Keeps project structure transparent
- Easier to coordinate across distributed teams
Setup
Build it in a few focused steps.
- 1Connect Notion and Agent mail to Notis.
- 2Tell Notis: 'When a new subpage is added under any of my project pages, send an email to the project team with the subpage title, creator, and a link to the new page.'
- 3Scope to your main project page (or pages).
- 4Pick a channel for run reports and test by adding a subpage to a project.
Questions about this workflow
Should I email the whole team or just the project lead?
You define this--typically the project lead and core team members.
Will this catch every new subpage, even drafts?
Yes, unless you scope it to only published or approved pages.
Can I exclude certain types of subpages?
Yes--specify what to exclude in your prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Agent mail. A trigger fires from one place; an action lands in another.
Notion triggers
Agent mail actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Message
Get a specific message from an agentmail inbox
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Messages
List messages from an agentmail inbox
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Send Email
Send an email using agentmail api
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Agent mail, 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 Agent mail.