Automatically notify team when database schemas change
When you update a database schema in Notion (add, rename, or remove columns), this workflow instantly lists your team. No more struggling to remember who uses that database or guessing about impact.
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
List Users
Tool to list users in a Google Workspace domain. Note: - When the provided base_url points to Currents News API (api.currentsapi.services), this action will gracefully fall back to listing latest news articles to ensure a valid response, since the Currents News API does not expose a users endpoint. - When the base_url points to Google Admin Directory API, it will list users from the domain/customer specified.
Why this helps
Schema changes in shared databases often break workflows or confuse team members who don't know what changed. Founders either over-communicate or under-communicate, creating friction.
- Ensure everyone knows about database structure changes immediately
- Identify impacted team members without guessing
- Reduce broken workflows caused by schema changes
- Maintain team confidence in shared databases
Setup
Build it in a few focused steps.
- 1Connect Notion and Currents API to Notis (portal, one time).
- 2Tell Notis: 'When a database schema changes in Notion, list the team members who use it.'
- 3Select Data Source Schema Updated trigger, optionally scope to specific data sources, and choose your channel.
- 4Make a test schema change (add or rename a column) and verify the team list appears.
- 5All future schema changes automatically generate team rosters.
Questions about this workflow
Does the team list include only people affected by the change?
No, it lists your entire team. You can then manually notify only the people who use that specific database.
Can I see what changed in the schema?
Yes. Your automation report includes the specific properties that were added, removed, or renamed so you know exactly what to communicate.
What if the schema changes frequently?
Each change triggers the workflow. If schema changes are frequent, consider batching notifications once daily instead.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Currents api. A trigger fires from one place; an action lands in another.
Notion triggers
Currents api actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Latest News
Tool to retrieve the latest news articles from Currents News API. Use when you need a real-time feed of recent articles.
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.
Activities Watch
Tool to start a notification channel to watch activities for a specified user and application. Use when needing to receive push notifications for user activity; call after OAuth credentials and webhook endpoint are set up.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Entity Usage Reports
Tool to retrieve usage statistics for a specific Google Workspace entity. Use when you need to analyze entity usage on a particular date.
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.
List Users
Tool to list users in a Google Workspace domain. Note: - When the provided base_url points to Currents News API (api.currentsapi.services), this action will gracefully fall back to listing latest news articles to ensure a valid response, since the Currents News API does not expose a users endpoint. - When the base_url points to Google Admin Directory API, it will list users from the domain/customer specified.
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 User Usage Report
Tool to retrieve the usage report for a specified user on a given date. Use after confirming the userKey and date. Use when detailed usage metrics are needed for auditing or monitoring.
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.
New Page
Triggers when a new page is added to a Notion database.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Connect any two apps with Notis in the middle.
Not just Notion and Currents api. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Currents api.