Keep operational schema changes visible
A new or renamed database property can change how work is tracked. Preserve that structural change in Mezmo.
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
Ingest logs to Mezmo
Tool to ingest log events to mezmo. use when sending structured logs from a host to mezmo log analysis.
Why this helps
Changes to tracking structure can quietly break team expectations and reports.
- Create a searchable record of schema changes.
- Make tracking structure changes visible to operators.
- Avoid relying on word of mouth for database updates.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mezmo to Notis once through the portal.
- 2Create an automation or tell Notis to ingest schema changes from a chosen operational data source into Mezmo.
- 3Choose the Notion Data Source Schema Updated trigger and select a channel for run reports.
- 4Rename or add a test property and review the log event in Mezmo.
Questions about this workflow
Does this cover adding a column?
Yes. The trigger reports data source schema updates, including column additions, removals, or renames.
Why use this trigger instead of page updates?
It provides a structural change signal and avoids relying on page property events emitted for existing rows when a column is added.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mezmo. A trigger fires from one place; an action lands in another.
Notion triggers
Mezmo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Pipeline Alert
Tool to delete an alert for a specific component within a pipeline. use after confirming pipeline id, component kind, component id, and alert id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Ingest logs to Mezmo
Tool to ingest log events to mezmo. use when sending structured logs from a host to mezmo log analysis.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Mezmo, 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 Mezmo.