Bring the Modelry product list into brief review
Start with a current view of Modelry products as soon as a new brief is written.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
List Modelry Products
Tool to list all products in modelry. use when you need to retrieve available products after authenticating.
Why this helps
A brief can move forward with assumptions about which Modelry products already exist.
- Make product review part of the brief workflow.
- Get an up-to-date catalog without manually opening Modelry.
- Reduce uncertainty before planning the next step.
Setup
Build it in a few focused steps.
- 1Connect Notion and Modelry to Notis once in the portal.
- 2Create an automation by asking Notis or opening Automations and choosing New Automation.
- 3Write one instruction asking Notis to list Modelry products when a new brief page is created and report the results.
- 4Select the Notion Page Created trigger and choose a channel for run reports.
- 5Test with one real brief page and check that the catalog report supports review.
Questions about this workflow
Will this create a product?
No. The selected Modelry action retrieves the product list for review.
Can the prompt say which briefs count?
Yes. State the intended brief pages in the plain-language instruction.
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.