Turn GitHub requests into Modelry modeling work
Capture the brief once, then let Notis prepare the Modelry order so the next step is obvious.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Order Modeling Service
Tool to place an order for 3d modeling services. use when workspace and product ids are known and modeling specifications are ready.
Why this helps
Important modeling requests get buried in issue queues or require copying context into another tool.
- Reduces duplicate entry between planning and modeling
- Keeps the original GitHub context attached to the request
- Creates a clear handoff for outsourced modeling work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Modelry to Notis once through the portal.
- 2Create an automation in Automations -> New Automation, or ask Notis to create it conversationally.
- 3Use one plain-language instruction: when a new GitHub issue requests product modeling, place a Modelry modeling order using the issue context and notify me if required details are missing.
- 4Select the GitHub new issue trigger, choose a run-report channel, and test with one real issue.
Questions about this workflow
Does Notis copy the issue into a separate form?
No. You describe the desired outcome in plain language, and Notis interprets the GitHub issue context when ordering the Modelry service.
What happens if the issue lacks specifications?
Have the instruction tell Notis to pause and report the missing information instead of placing an incomplete order.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Modelry. A trigger fires from one place; an action lands in another.
GitHub triggers
Modelry actions
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.
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.
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.
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).
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Modelry Product
Tool to delete a product. use after confirming the product id.
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.
Delete Product Repository
Tool to delete a product repository. use after confirming the repository id.
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.
Delete Modelry Workspace
Tool to delete a workspace. use after confirming the workspace 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.
Get Embed
Tool to retrieve details of a specific embed. use after confirming the embed id.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get Product Repository
Tool to retrieve details of a specific product repository. use when you have a repository id and need its details.
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Modelry. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Modelry.