Jira
Every client note becomes a Jira issue with the client's words and a link back to the exact spot on the model.
- Issue done in Jira, note resolved in MeshMarkup
- The issue and its status shown on the note
Notes pinned on your 3D models go straight to your board, your chat and your folders, with a link back to the exact spot. Finish the task there and the note is resolved here.
1 · Your client
3Base plateOPEN
Both bolts should sit flush, countersunk into the base.
pins a note on the model, through your review link.
2 · Your team
#3 Base plate: Both bolts should sit flush…
Jira · To do · link to the note
Ana left a note on pillow-block v2
gets it as a task, and a heads-up in chat.
3 · Done there, resolved here
3Base plateRESOLVED
Resolved by Jira
Your client sees it the next time they open the link.
Project management
Your team keeps working in the board it already lives in. Every note a client pins arrives there as a task with a link back to the exact spot, and finishing the task resolves the note.
Every client note becomes a Jira issue with the client's words and a link back to the exact spot on the model.
Every client note becomes an Asana task in the project and section you choose.
Every client note becomes a card on your board, in the list you choose.
Every client note becomes a ClickUp task in the list you choose.
Chat
A short message when a client leaves notes or signs off, batched so a busy review is one message, not twenty.
A message in your channel when a client leaves notes, replies or signs off, batched so the channel stays readable.
The same updates in a Microsoft Teams channel, as a card your team can open straight from the chat.
The same updates in a Discord channel, for studios that run on Discord.
Files
Point MeshMarkup at the folder you already export to. New files become models, changed ones new versions, and approved versions are copied back.
Point MeshMarkup at a Dropbox folder: new files become models, changed files new versions.
Automation
Triggers and actions for Zapier and Make, and a full API with signed webhooks for your own pipeline.
Connect MeshMarkup to thousands of apps without code: new notes, replies, approvals and opened links as triggers.
The same triggers and actions in Make scenarios, for teams that build their automations there.
Read and write models, notes and review links from your own tools, and get a signed webhook for every event.
Where you model
Skip the export-and-upload step.
Send the scene for review straight from Blender and see the notes come back, without exporting by hand.
Sign-in
Single sign-on for studios on Pipeline. When someone leaves the company, their access to MeshMarkup goes with their company account.
Your team signs in with the company account they already use, through Okta, Microsoft Entra ID, Google Workspace or any SAML provider.
Finish the task in your tool and the note is resolved in MeshMarkup. Nobody closes things twice.
Every task, message and file links to the note on the model, in the view the client left it from.
The note, the client's words, the model's name. Never your 3D files, unless you copy approved ones to your own folder.
Solo, Studio and Pipeline. The Blender add-on works on every plan, Free included; single sign-on is part of Pipeline. Every paid plan starts with a free trial.
No. Your client still just opens the link and pins notes. The integrations work on your side: they carry the notes to your team's tools.
A client note becomes a task in your tool, and when that task is finished there, MeshMarkup resolves the note. Nobody has to close things twice.
Only what the integration needs: the note, the client's words, the model's name and a link back. Never the 3D file, except to a folder you chose to copy approved versions into.
Zapier and Make reach thousands of apps, and the API covers the rest. Or tell us which one you use: we add integrations people ask for.
Start free, send a model for review, and connect your team’s tools when you’re ready.