Stay informed when a Notion database changes shape
A small alert can save time when a familiar database gains or loses a column.
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
Publish Message to Topic (PUT)
Tool to publish a message to a topic using PUT method. Use when you need to send notifications to subscribers of a topic. Supports various options like priority, tags, attachments, and scheduled delivery.
Why this helps
Structural changes to a database can disrupt routines and assumptions about where information belongs.
- Notice columns added, removed, or renamed.
- Understand when a familiar database workflow may need adjustment.
- Avoid discovering structural changes only after something breaks.
Setup
Build it in a few focused steps.
- 1Connect Notion and ntfy to Notis once in the portal.
- 2Create an automation and describe in plain language that data source schema changes should send an ntfy summary.
- 3Select Data Source Schema Updated and scope it to the relevant data source if desired.
- 4Choose a channel for run reports and test after a real column change.
Questions about this workflow
Does this catch renamed columns?
Yes. The event reports schema updates and includes the updated property action.
Will adding a column also send row alerts?
Notion may emit page property update events for existing rows when a column is added. Use the schema-specific trigger for a single structural-change signal.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ntfy. A trigger fires from one place; an action lands in another.
Notion triggers
Ntfy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create NTFY Account
Tool to register a new user account on ntfy. Use when you need to create a new user account on the ntfy.sh hosted service. Note: This endpoint is not available on self-hosted instances unless signup is explicitly enabled in the server configuration.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Web Push Subscription
Tool to register a web push subscription for browser notifications. Use when you need to enable push notifications from ntfy topics through a browser's native push notification system.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Web Push Subscription
Tool to unregister a web push subscription from the ntfy server. Use when you need to remove browser push notifications for a previously registered endpoint.
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.
Fetch Cached Messages
Tool to fetch cached messages from a ntfy topic. Use when you need to retrieve previously sent messages stored on the server. Supports filtering by time (duration or timestamp), message ID, content, title, priority, and tags. Set poll=1 to return immediately after fetching available cached messages.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Fetch Latest Message from Topic
Tool to fetch the most recent message from a topic's cache. Use when you need to retrieve the latest message without subscribing to the topic stream.
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.
Fetch Scheduled Messages
Tool to fetch messages scheduled for later delivery from a topic. Use when you need to retrieve messages that are set to be delivered at a future date. The poll=1 and scheduled=1 parameters are automatically set to retrieve cached scheduled messages in a single request.
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.
Get Account Information
Tool to retrieve account data for authenticated user or anonymous user. Use when you need to get account information, limits, statistics, or tier details.
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.
Get Server Statistics
Tool to retrieve server statistics including message counts and publishing rates. Use when you need to monitor ntfy server activity and get metrics about message volume.
Connect any two apps with Notis in the middle.
Notion and Ntfy, 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 Ntfy.