Keep visual planning guidance aligned with database changes
When a Notion data source changes shape, prompt a review of the board guidance that helps everyone use it consistently.
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
Update Board
Tool to update properties of a specific board. use when you have a board id and need to modify its name, description, or permissions policy. use after confirming the board exists.
Why this helps
Changes to database structure can leave workflow instructions and team expectations stale.
- Prompt review when a data source gains, loses, or renames a property.
- Keep board guidance from silently drifting out of date.
- Make structural changes easier to discuss as a team.
Setup
Build it in a few focused steps.
- 1Connect Notion and Miro to Notis once through the portal.
- 2Create an automation with a plain-language instruction to update the relevant Miro board guidance after a schema change.
- 3Select Data Source Schema Updated, optionally scoped to a data source, and choose a channel for run reports.
- 4Test with an approved schema change and check the board description for a clear review prompt.
Questions about this workflow
Does this run for individual row edits?
No. It watches schema updates such as property additions, removals, or renames.
Can it be limited to one data source?
Yes. The trigger supports an optional data_source_id scope.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Miro. A trigger fires from one place; an action lands in another.
Notion triggers
Miro actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Board
Tool to create a new board. use when you need to set up a board with a specific name, description, and policies. example: "create a new board named project plan".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete App Card Item
Tool to delete an app card item from a board. use when you need to remove an app card item created by your app after it is no longer needed.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Document Item
Tool to delete a document item from a board. use when you need to remove a document item (e.g., pdf or image) that is no longer relevant. example: "delete the document item with id 'item456' from board 'board123'."
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.
Delete Item
Tool to delete a specific item from a board. use when you need to remove an item (e.g., shape, sticky note) after confirming its board and item ids.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get App Card Item
Tool to retrieve a specific app card item by its id. use when you need the details of an existing app card item.
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.
Get Board
Tool to retrieve details of a specific board. use when you have a board id and need to fetch its metadata.
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 Board Members
Tool to retrieve a list of members for a board. use when you need to list all users with access to a board after confirming its id.
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 Boards
Tool to retrieve accessible boards with optional filters. use when you need to list or search boards by team, project, owner, or keywords.
Connect any two apps with Notis in the middle.
Notion and Miro, 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 Miro.