Make
Connect MeshMarkup to thousands of apps with Make: new notes, replies, approvals and opened links as triggers; review links, replies and note statuses as actions.
With Make, MeshMarkup can talk to almost any other app without code: put each client note in Notion or Airtable, log approvals in a spreadsheet, send a review link from your CRM, or post to a tool MeshMarkup doesn't connect to directly.
Connect Make
Make an API key
In MeshMarkup open Settings → Integrations and click API keys on the API and webhooks card. Name the key Make, leave Read only unticked, click Create key and copy it. It's shown once.
Open MeshMarkup in Make
Click Open in Make on the Make card. Open the invitation, install the MeshMarkup app in your Make organization, then add a MeshMarkup module to a scenario.
Connect your account
Click Create a connection when Make asks, and paste the key. The connection is named after your studio.
Triggers
| Trigger | When |
|---|---|
| New Note | A reviewer pins a new note on a model or an image |
| New Reply | Someone replies on a note (internal replies are never sent) |
| Note Resolved | A note is marked resolved |
| Version Approved | A client signs off a version |
| New Version Uploaded | A new version of a model is uploaded |
| Review Link Opened | A client opens a review link for the first time |
Each one carries the model's name, the version, and for notes the note's number, part, status and text, plus a Model link and a Note link that open MeshMarkup on the spot. MeshMarkup sends them to Make in batches, so a trigger fires within the hour.
Actions
| Action | Does |
|---|---|
| Create Review Link | Makes a review link on a model's latest version (or one you name): feedback, look only, or sign-off (Solo and up) |
| Reply to Note | Adds a reply, for the client or internal |
| Update Note Status | Open, in progress, resolved or won't fix |
There's also Find Model to look a model up by name and Make an API call for any other endpoint.
A two-way example
Note → task
Trigger: New Note. Action: create a task in your tool with the Note text as its title and the Note link in its description. Keep the Note ID in the task.
Task done → note resolved
Trigger: your tool's task completed. Action: Update Note Status with that Note ID and Resolved.
Good to know
- Replies and links made through Make carry the name of whoever created the API key.
- Turning a scenario off unsubscribes it straight away. Revoking the API key stops every scenario that used it.
- Using Jira, Asana, Trello, monday.com, ClickUp or Linear? A direct connection may already do this for you; see Integrations.
Was this guide helpful?
Related guides
Get feedback on the model, not on a screenshot
Upload a model, send one link, and your client clicks the exact spot. Free to start — no card.