Never Miss a Data Structure Change
Schema changes don't pass silently anymore. Right person is notified automatically.
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
Get Current User
Tool to retrieve current user information. Use after authenticating with your API key to verify identity.
Why this helps
A column gets added or removed in your Notion data source, but nobody notices. Later, you realize data is missing or workflows are broken.
- Responsible person is notified immediately when schema changes
- Catch misconfiguration before data breaks
- Clear record of who made schema changes and when
- Prevent silent data structure issues
Setup
Build it in a few focused steps.
- 1Connect Algodocs and Notion integrations to Notis
- 2Create automation: 'Schema Change Alert'
- 3Set trigger to 'Data Source Schema Updated' for your critical data sources
- 4Write instruction: 'When a data source schema changes, get the current user and notify them of the change'
- 5Test by adding a new column to a data source and verify notification
Questions about this workflow
Which data sources should I monitor?
Start with your critical business databases (customers, transactions, products). You can add more over time.
Can I get historical record of all schema changes?
Yes, Notis logs all automation runs. Check the automation history for a complete audit trail.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Algodocs. A trigger fires from one place; an action lands in another.
Notion triggers
Algodocs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current User
Tool to retrieve current user information. Use after authenticating with your API key to verify identity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List document data extractors
Tool to list document data extractors. Use when you need identifiers and names of all extractors in your AlgoDocs account.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List folders
Tool to list folders. Use when you need to retrieve all folder IDs and their hierarchy. Must be called after obtaining an API key.
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 Algodocs, 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 Algodocs.