Auto-Email Meeting Decisions When Notes Are Updated
When meeting notes are captured or updated in Notion, auto-email a summary of all decisions and action items to stakeholders--no manual forwarding required.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Send Email
Send an email using agentmail api
Why this helps
Meeting notes sit in Notion. People who weren't in the meeting don't know there's a decision, action items go undone, and important commitments fall through.
- Everyone knows about decisions without waiting for manual emails
- Action items are visible and assigned from day one
- Reduces rework from people missing key commitments
- Creates accountability through automatic distribution
Setup
Build it in a few focused steps.
- 1Connect Notion and Agent mail to Notis.
- 2Tell Notis: 'When a Notion page in my Meeting Notes database is updated, send an email to everyone mentioned listing all decisions, action items, owners, and deadlines.'
- 3Scope to your meeting notes database.
- 4Pick a channel for run reports and test with a real meeting note update.
Questions about this workflow
Will team members get an email every time I edit the notes?
Yes--consider having a 'final' or 'published' status to avoid repeated emails during the drafting phase.
Can I limit the email to only action items (not all content)?
Absolutely. Tell Notis to extract only the action item section and email that.
What if notes are updated after hours?
The email sends right away, or you can delay it to working hours in your setup.
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.