Make embed review part of a project status change
Use a status update as a cue to see which Modelry embeds are available.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
List Embeds
Tool to list available embeds. use when you need embed ids for downstream actions (e.g., modelry get embed). supports optional pagination.
Why this helps
Embed details can be overlooked when a project status changes and attention shifts to the next task.
- Bring embed visibility into a status transition.
- Reduce context switching during project handoffs.
- Receive a report that supports a focused next step.
Setup
Build it in a few focused steps.
- 1Connect Notion and Modelry to Notis once in the portal.
- 2Ask Notis to create an automation or start one in the portal's Automations area.
- 3Describe in one prompt when a status change should prompt a Modelry embed list and report.
- 4Pick the Notion Page Properties Updated trigger and choose a channel for run reports.
- 5Test with one real status update and review the resulting inventory.
Questions about this workflow
Can I have this run only for a certain property change?
Describe the relevant status change in the prompt; the event includes updated property information for downstream interpretation.
Does it retrieve embed details?
This workflow lists embeds. A separate workflow can retrieve a specific embed when its ID is known.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Modelry. A trigger fires from one place; an action lands in another.
Notion triggers
Modelry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Workspace
Tool to create a new workspace. use when you need to group products and embeds into a dedicated workspace. call after authenticating and specifying workspace details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Modelry Embed
Tool to delete an embed. tries multiple common endpoint patterns and treats 404 as idempotent success after exhausting candidates (embed already deleted or not found).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Modelry Product
Tool to delete a product. use after confirming the product id.
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 Product Repository
Tool to delete a product repository. use after confirming the repository id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Modelry Workspace
Tool to delete a workspace. use after confirming the workspace id.
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 Embed
Tool to retrieve details of a specific embed. use after confirming the embed 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.
Get Product Repository
Tool to retrieve details of a specific product repository. use when you have a repository id and need its 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 Workspace
Tool to retrieve details for a specific workspace. use after confirming the workspace id.
Connect any two apps with Notis in the middle.
Notion and Modelry, 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 Modelry.