Turn Notion incident records into searchable Mezmo logs
Capture the incident once in Notion and let Notis send its useful context to Mezmo for later investigation.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
Manually copying incident details into logging tools adds another step during an already distracting incident.
- Keep incident context searchable in Mezmo.
- Reduce duplicate entry during incident response.
- Give the team a consistent record of new incidents.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mezmo to Notis once in the portal.
- 2Create an automation in the portal, or tell Notis in plain language to log new Notion incident records in Mezmo.
- 3Select the Notion New Page trigger for the incident database and choose a channel for run reports.
- 4Test with one real incident record and review the resulting Mezmo log.
Questions about this workflow
Does this create a Mezmo log for every new incident record?
Yes. The automation responds to new Notion pages in the selected database and asks Notis to ingest a structured log in Mezmo.
Do I need to map database properties?
No. Describe in the prompt which incident details should be included, and Notis interprets the instruction.
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.