Archive the right Matterport model from a reviewed GitHub request
Retire an outdated virtual tour through a clear review step: add the archive-approved label to the GitHub issue that names the exact Matterport model, and Notis can set that model inactive.
Trigger
GitHub Issue Labels Changed
Triggers when the labels on a specific GitHub issue change. Fires whenever a label is added to, removed from, or has its metadata (color, description) modified on the monitored issue. The payload includes: - ``current_labels`` -- the full set of labels currently on the issue - ``added_labels`` -- labels that were newly added - ``removed_label_names`` -- names of labels that were removed - ``changed_label_names`` -- labels whose metadata changed without being added or removed
Action
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.
Why this helps
A superseded or retired virtual tour can remain active because the request, approval, and model administration live in separate places.
- Require a deliberate approval label before changing a model's state.
- Use an exact Matterport model ID from the existing GitHub issue instead of guessing which tour to update.
- Set the model inactive for archiving without permanently deleting it.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Matterport to Notis once, and agree that only an authorized reviewer may apply your dedicated archive-approved label.
- 2Create the automation in the portal or ask Notis conversationally; instruct it to retrieve the existing issue and set a Matterport model inactive only when the label was newly added and the issue contains one exact model ID.
- 3Choose the GitHub issue labels changed trigger for the relevant repository and select a channel for run reports.
- 4Test with one reviewed issue and a non-critical model, then verify the intended model is inactive and no other model was changed.
Questions about this workflow
Does this permanently delete a Matterport model?
No. The action changes a model between active and inactive, where inactive is the archived state. It does not permanently delete the model.
Will any issue label change archive a model?
No. Instruct Notis to act only when the dedicated approval label is newly added and the issue contains one exact Matterport model ID. Skip missing or ambiguous IDs.
Does the label-change trigger include the model ID?
The trigger description guarantees label-change details, not the issue body. Have Notis retrieve the existing GitHub issue before proceeding.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Matterport. A trigger fires from one place; an action lands in another.
GitHub 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.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
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).
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
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.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub 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.