Integrations

Integrations send what happens in MeshMarkup (new notes, replies, sign-offs) to the tools your team already works in, and let those tools act back: resolve a note when its task is done, make a review link, reply. You'll find them all under Settings → Integrations. An owner or admin sets them up; members can see what's connected.

#Chat channels

MeshMarkup posts into a channel when a reviewer leaves a note or replies, a client approves a version, a new version is uploaded, or a note is resolved. Posts are batched like the emails, so a client working through a model for a few minutes produces one message with an Open button for the model, not one per click.

Each chat app gives you a webhook URL for one channel. You paste it on the card and click Connect. MeshMarkup posts a test message (MeshMarkup is connected…) before saving, so a mistyped URL fails straight away. After that, nobody can read the URL back from the page.

#Slack

1. 1

   Create an incoming webhook

   In Slack, go to Apps›Incoming Webhooks›Add to Slack, pick the channel and copy the Webhook URL. It starts with https://hooks.slack.com/services/.

2. 2

   Connect it

   On Settings → Integrations, click Connect on the Slack card, paste the URL, optionally type the channel name for your team's reference, and click Connect.

More detail in email notifications and Slack.

#Microsoft Teams

1. 1

   Add a workflow to the channel

   In Teams, open the channel, click ••• next to its name, choose Workflows, then the template Post to a channel when a webhook request is received. Follow the steps (Teams asks which team and channel) and copy the URL it shows at the end.

2. 2

   Connect it

   Click Connect on the Microsoft Teams card, paste the URL and click Connect.

More detail: connect Microsoft Teams.

#Discord

1. 1

   Create a webhook

   In Discord, open Server Settings → Integrations → Webhooks, click New Webhook, choose the channel and click Copy Webhook URL.

2. 2

   Connect it

   Click Connect on the Discord card, paste the URL and click Connect.

Posts appear from MeshMarkup. Names typed by clients can never ping @everyone.

More detail: connect Discord.

#Disconnecting

Click Disconnect under the card. Posts stop straight away. Disconnecting works on any plan, so you can switch a channel off after a downgrade too.

#Project management tools

Connect your team's tool and every new note a client leaves becomes a task there, with the client's words, the model, the version and a link straight back to the note. On the model page, the note shows the task with its current status, so you can jump across. When the task is finished in the tool, MeshMarkup resolves the note, with the tool's name on it, and checks again about once an hour.

1. 1

   Connect

   On Settings → Integrations, click Connect on the tool's card. You go to the tool's own page to allow MeshMarkup in; you come back to MeshMarkup when you've approved it.

2. 2

   Choose where tasks go

   The card opens Where should client notes go? Pick from the lists, which come from your own account, then click Save. The card then says On, with your account name and where new notes go.

3. 3

   Leave a test note

   Open a review link as a client would and leave a note. It appears in your tool within the hour.

Notes your studio leaves itself aren't sent; only your client's are. Untick Send every new client note (click Change first) to pause without disconnecting. Disconnect stops new tasks; the ones already made stay in your tool, linked to their notes. If the tool stops accepting the connection (a password change, or access removed), the card says Needs reconnecting with a Reconnect link.

A note carried onto a new version keeps its task: finishing the task resolves the note on the latest version too.

#Jira

Pick the Site (if you have more than one), the Project and the Issue type. Each client note becomes an issue. An issue is done when Jira puts its status in the Done category, whatever your workflow calls it.

Step by step: connect Jira.

#Asana

Pick the Workspace, the Project and, if you like, the Section new tasks go into. Each client note becomes a task. A task is done when it's marked complete.

Step by step: connect Asana.

#Trello

Pick the Board and the list New cards go to. Optionally pick the list that means done. Each client note becomes a card. A card is done when it's archived, its due date is ticked complete, or it's moved to the done list you picked (if you didn't pick one: any list whose name starts with Done or Complete).

Step by step: connect Trello.

#ClickUp

Pick the Workspace, the Space and the List. Each client note becomes a task. A task is done when it reaches a closed or done status.

Step by step: connect ClickUp.

#Files

Point MeshMarkup at the folder you already save your exports to, in Dropbox. Each hour it looks inside: a new 3D file becomes a model, and a file saved again becomes the next version. A GLB comes in on its own; other formats are converted in your browser, so the Models page shows them as ready to import until someone clicks Import. Approved versions can be copied back into an Approved folder inside it.

• Connect Dropbox

#Zapier and Make

With Zapier or Make, MeshMarkup connects to thousands of other apps without code: put each client note in Notion or Airtable, log approvals in a spreadsheet, send a review link from your CRM.

You connect with an API key:

1. 1

   Make a key

   On Settings → Integrations, click API keys on the API and webhooks card. Name the key after what will use it, leave Read only unticked, and click Create key. Copy it; it's shown once.

2. 2

   Connect in Zapier or Make

   Click Open in … on its card, add MeshMarkup to a Zap or scenario, and paste the key when it asks for it. The connection is named after your studio.

Triggers (something happened in MeshMarkup): New note, New reply, Note resolved, Version approved, New version uploaded, and Review link opened (the first time a client opens it). Each one carries the model, the version, the note's number, part, status and text, and links straight to the model and to the note.

Actions (do something in MeshMarkup): Create a review link, Reply to a note, and Update a note's status. Search: Find a model by name.

#A two-way example

To turn client notes into tasks and resolve them when the task is done:

1. 1

   Note → task

   Trigger: MeshMarkup — New Note. Action: create a task in your tool, with the Note text as its title and the Note link in its description. Store the Note ID in the task too (a custom field, or the end of the description).

2. 2

   Task done → note resolved

   Trigger: your tool's task completed. Action: MeshMarkup — Update Note Status, with the Note ID from the task and status Resolved.

The note is resolved on the model, with your team's name on it, and the client sees it the next time they open the link.

Step by step: Zapier.

Step by step: Make.

#Single sign-on

On Pipeline, your team can sign in with your company's identity provider (Okta, Microsoft Entra ID, Google Workspace or any SAML provider) and join your studio on their first sign-in. See single sign-on.

#API and webhooks

For your own tools, the same events arrive as signed webhooks, and the API reads and writes models, notes and review links. See the API and webhooks.

#The Blender add-on

Send the scene for review from Blender and see the notes come back, on any plan. See MeshMarkup for Blender.