Skip to main content
Make is a workflow automation platform that connects apps into scenarios. The official SudoMock app covers the render API. From inside a scenario you can upload a PSD, render it with new artwork, turn a product photo into a reusable mockup, render a short video, and hand the finished file to the next module.

​
Install the app

1

Add SudoMock to your Make organization

Open the SudoMock app invitation and accept it while signed in to Make. The app then appears in the module picker of every scenario in that organization.
2

Create an API key

Create a key in your dashboard and copy it once. Confirm it is live before you build the scenario:
3

Add your SudoMock connection

Add any SudoMock module to a scenario. Make asks for a connection the first time. Paste the key into API key. Make verifies it against your account and shows the matching email, so a wrong key fails at setup instead of mid run.
4

Render your first mockup

Add the Render a mockup module, pick your connection, enter the mockup UUID, and map a design URL onto the smart object you want to fill. Run the scenario once. Upload a PSD first if you do not have a template yet.
The finished image URL arrives on the module output at data.print_files[0].export_path. Map it straight into the next module.

​
Modules

Get PSD mockup layers lists every layer of a template with its UUID, including the layers inside its smart objects. Map some of those UUIDs into Hidden layers on Render a mockup to leave those layers out of one render; the template itself does not change. Make an API call reaches any endpoint that has no module of its own. Enter a path below https://api.sudomock.com, including the API version. The connection supplies the key, so do not add a header yourself.

​
Long renders and the Get a job module

A render sent with is_async returns a job id right away, so a scenario never waits on the response. Follow it with the Get a job module and branch on the status field. The first three mean the work is still in flight. The last three are terminal, so a router that stops on those three never loops forever. Every field is on the jobs endpoint.

​
An example scenario

Here is a scenario you can build with two modules:
  1. Google Sheets watches a sheet for new rows.
  2. SudoMock renders the template using the design URL from that row.
The trigger and action pattern works with any app Make connects. Post the finished image to a chat channel, write it back to the sheet, or push it to a store listing.
Every SudoMock module reads the same connection, so one key is enough for a whole organization.