Alert the Team When Database Structure Changes in Notion
When someone adds, removes, or renames a property in a Notion database, the team gets an email describing what changed--preventing confusion and broken workflows.
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
Send Email
Send an email using agentmail api
Why this helps
Database structures change silently. People rely on columns that disappear, workflows break, and no one knows why. Schema change alerts prevent downstream surprises.
- Team discovers structural changes immediately
- Prevents workflows from breaking silently
- Reduces confusion about missing or renamed fields
- Improves data governance
Setup
Build it in a few focused steps.
- 1Connect Notion to Notis.
- 2Tell Notis: 'When a property is added, removed, or renamed in any of my databases, send an email to database admins and affected teams with the database name, property name, and what changed (added/removed/renamed).'
- 3Scope to specific databases or leave open for all.
- 4Pick a channel for run reports and test by adding a new property to a database.
Questions about this workflow
Won't this email often (especially if people add temp columns)?
Yes--some teams prefer weekly digests of schema changes instead of real-time emails.
Should all team members get notified or just admins?
Typically just admins and affected teams, not the whole company.
Can I see what the old value was if a property is renamed?
Yes--Notis can include the old name in the notification.
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.