Capture, share, and collaborate the built world in immersive 3D
Capture, share, and collaborate the built world in immersive 3D On Nagent, Matterport is exposed as a fully-configurable developer tools integration that any agent can call — 6 actions, and BASIC, OAUTH2 authentication. No code is required to wire Matterport into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Matterport to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Matterport into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Matterport, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MATTERPORT_DELETE_MODELTool to permanently delete a Matterport model. Use when you need to remove a model entirely from the Matterport platform. This operation is irreversible.
Input parameters
Unique identifier of the Matterport model to be permanently deleted
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MATTERPORT_MODELTool 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.
Input parameters
Unique identifier of the Matterport model to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MATTERPORT_MODEL_EVENT_WEBHOOK_CALLBACKSTool 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).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MATTERPORT_MODELSTool 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.
Input parameters
Free text search string for models. Use '*' for all models, or provide specific search terms. If unspecified, all models within the organization are returned
Offset ID for pagination. Use the 'nextOffset' value from a previous response to retrieve the next page of results
Determines result ordering. Valid values: 'created' (creation timestamp), 'modified' (modification timestamp), 'name' (alphabetical). Defaults to creation timestamp descending if not specified
Include additional models in non-active states. Valid values: 'demo' (include demo models), 'inactive' (include archived models)
Maximum number of results per page. Maximum allowed is 1000, default is 10
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MATTERPORT_ROOM_CLASSIFICATIONSTool 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MATTERPORT_UPDATE_MODEL_STATETool 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.
Input parameters
The model identifier to modify
Specifies which ID field to use for lookup. Valid values: 'id' (primary identifier), 'internalId' (internal system identifier), 'mlsId' (MLS identifier). Defaults to primary identifier if not specified
Target state for the model. Use 'active' to unarchive the model or 'inactive' to archive the model
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 78 agents privately built on Nagent that already use Matterport.
Build on Nagent
Connect Matterport to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Matterport, and click "Connect Now." You'll authenticate with BASIC, OAUTH2 — Nagent handles credential storage and refresh automatically. Once connected, Matterport is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Matterport is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Matterport steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Matterport event fires, the agent kicks off automatically.
Every Matterport action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Matterport ships with 6 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Matterport together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Matterport-based workflows tailored to your business.