Find relevant Matterport models from updated facility notes
Update a facilities page and let Notis search Matterport for the spaces connected to the new information.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Query Matterport Models
Tool to retrieve a page of Matterport models with optional search and filtering. Use when you need to list, search, or filter models within an organization.
Why this helps
Facility updates can be easy to miss when the corresponding virtual space is stored in a separate tool.
- Connect updated facility notes to a model search.
- Reduce manual lookups when a space issue changes.
- Help teams find virtual context alongside operational notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Matterport to Notis once through the portal.
- 2Ask Notis to search Matterport for models that match the updated facility notes and report the strongest matches.
- 3Select the Notion Page Content Updated trigger for the facilities page or data source.
- 4Choose a run report channel and test with one real facilities edit.
Questions about this workflow
Will this find every related model?
Search results depend on available model information and the matching details described in the prompt.
Can I limit it to one facility page?
Scope the content-updated trigger to a specific page when that is the desired coverage.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Matterport. A trigger fires from one place; an action lands in another.
Notion triggers
Matterport actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Matterport Model
Tool to permanently delete a Matterport model. Use when you need to remove a model entirely from the Matterport platform. This operation is irreversible.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Model by ID
Tool to retrieve detailed information about a single Matterport 3D model by its ID. Use when you need to fetch model metadata, publication details, spatial information, or other properties of a specific Matterport model.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Model Event Webhook Callbacks
Tool to retrieve a list of registered webhook callback configurations for model events. Use when you need to view all configured webhooks that receive notifications when model events occur (e.g., created, deleted, updated, processed, transferred).
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.
Query Matterport Models
Tool to retrieve a page of Matterport models with optional search and filtering. Use when you need to list, search, or filter models within an organization.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Room Classifications
Tool to list all room classifications defined for Matterport room classification models. Use when you need to retrieve the available room types and their associated keywords.
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.
Update Model State
Tool to change a Matterport model between active and inactive (archived) states. Use when you need to archive an inactive model or unarchive an active model. This operation is idempotent.
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 Matterport, 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 Matterport.