Skip to content
Notis

Connect Lyzr to Matterport

When something happens in Lyzr, Notis takes the next step in Matterport. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Lyzr to Matterport

View example

Keep an agent-ready Matterport space catalog

When your Lyzr workspace sends a request, find Matterport spaces matching the project or property context so an agent can work from the right virtual environment.

View example

Review the Matterport library on a steady cadence

Have Notis periodically query Matterport models so your Lyzr-supported operations can review the current space inventory without remembering to start a manual search.

View example

Fetch model details when an agent needs them

When a Lyzr process supplies a Matterport model ID to Notis, retrieve that model's details for the next step in the workflow.

View example

Check Matterport model notification setup

On a recurring schedule, retrieve configured Matterport model event callbacks so your team can review whether expected notifications are registered.

View example

Look up room classifications for an agent

When a Lyzr process needs a room-type reference, let Notis retrieve Matterport's available room classifications and associated keywords.

View example

Archive selected inactive Matterport models

On a scheduled review cadence, ask Notis to use an approved list from your Lyzr operations to archive Matterport models that are confirmed inactive.

View example

Archive a project space after closeout

When a Lyzr closeout process sends a confirmed Matterport model ID to Notis, change its state to inactive to keep the active collection current.

View example

Reactivate a Matterport space on request

When a Lyzr workflow requests a previously archived space for renewed work, ask Notis to set the specified Matterport model active.

View example

Start the day with a space availability check

On chosen weekdays, query Matterport models so your Lyzr-supported operations can review which spaces are available for upcoming work.

Supported Triggers and Actions

Notis builds workflows that link Lyzr to Matterport. A trigger fires from one place; an action lands in another.

Lyzr triggers

Matterport actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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).

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant
Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only
Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match
Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

Notis

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Connect any two apps with Notis in the middle.

Lyzr 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.