Resources · Make integration

Dynamic Mockups Make integrationAutomate Dynamic Mockups with Make.

What if every new design came back as a finished mockup image, without opening an editor? The Dynamic Mockups Make integration gives you 2 action modules. This guide is for shops and marketing teams: connect your API key, then build a first scenario that renders a mockup.

Try the Dynamic Mockups integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Dynamic Mockups Make integration do?

The Dynamic Mockups Make integration lets a Make scenario (the automation you build, a chain of modules) send a design to Dynamic Mockups and get back the URL of a finished mockup image. You pick the mockup template, pass the design asset, and the result is ready for the next step, with no code.

Product pages that fill themselves. A print-on-demand store adds a new artwork in another app; Create a Mockup Render places it on the chosen template and returns an image URL that the next module can drop into a product listing.

Campaign visuals without the design queue. A marketer approves a logo or a slogan, and the scenario renders it on a t-shirt or mug template so the social post has its picture.

Anything the listed modules skip. Make an API Call reaches any other endpoint of the Dynamic Mockups API with the same connection (your account linked to Make once).

What Make does not do here: the app has no trigger, so a scenario starts from another app or from Make's own schedule, and the connection needs a paid Dynamic Mockups account. The same app may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ. To learn the editor itself, see the Make training, and check the Make pricing page before you scale up.

Connect

How do you connect Dynamic Mockups to Make?

  1. 01

    Create an API key in Dynamic Mockups

    Log in to Dynamic Mockups, click API Integration in the left sidebar, then Create API Key. Give the key a name, click Create, and copy the value somewhere safe.

  2. 02

    Open the connection window in Make

    Add a Dynamic Mockups module to your scenario and click Create a connection. The Connection name field is optional, but a clear name helps when several people share one Make account.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. If Make asks you to authenticate your account and confirm access, accept, and every Dynamic Mockups module in your scenarios will reuse this connection.

First scenario

Your first scenario with Dynamic Mockups

GoalWhen a new design shows up in another app, Make renders it on a Dynamic Mockups template and passes the image URL along.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Dynamic Mockups has no trigger, so this first module comes from the app where your designs live.

  2. 02

    Set the starting module

    Pick the trigger of that other app and link its account. Each design it finds becomes a bundle, one item passed from a module to the next.

  3. 03

    Add Create a Mockup Render

    Click the + on the right, search Dynamic Mockups and pick Create a Mockup Render. Choose your connection, select the mockup template, and map the design asset from the previous module.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bundles of the Dynamic Mockups module and check that an image URL came back before you add anything after it.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What can Dynamic Mockups do in Make?

Dynamic Mockups gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Dynamic Mockups1

Create a Mockup Render

Action

In Make“Returns an image URL of the selected mockup template and provided design asset.”

This module takes a design asset, places it on the mockup template you select, and hands back the URL of the rendered image. That URL is what later modules use to publish, store or send the picture.

When to use it
a new artwork or logo is approved and you want a ready product visual without opening the Dynamic Mockups editor.
Watch out
the output is a link, not a file, so map the URL into the next module rather than expecting an attachment.
Dynamic Mockups2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Dynamic Mockups API from inside your scenario, signed with the connection you already set up. It covers whatever the render module does not offer, with no second key to manage.

When to use it
you need an API feature of Dynamic Mockups that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Dynamic Mockups API documentation open next to the module.
Need help

Need help automating Dynamic Mockups with Make?

A person reads every message.

FAQ

Dynamic Mockups and Make: common questions

01Is the Dynamic Mockups Make integration free?
On the Make side, yes: Dynamic Mockups is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, and caps files at 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in operations per month. On the Dynamic Mockups side, the connection requires a paid account, so the app subscription is the part that is not free.
02What do you need to connect Dynamic Mockups to Make?
You need a paid Dynamic Mockups account and an API key. In Dynamic Mockups, open API Integration in the left sidebar, click Create API Key, name it and copy the value. In Make, add a Dynamic Mockups module, click Create a connection, paste the key into the API Key field and click Save. If Make asks you to confirm access, accept. The connection is then reused by both Dynamic Mockups modules.
03Does Dynamic Mockups trigger Make scenarios in real time?
No, because Dynamic Mockups has no trigger module in Make: it only provides actions. A scenario therefore starts elsewhere, either on a trigger from the app that holds your designs, or on Make's own schedule set on the first module, every 15 minutes by default and down to 1 minute on paid plans. If that first module is an instant trigger of another app, the render follows the event as soon as that app calls Make.
04What if Dynamic Mockups is missing a module you need in Make?
Use Make an API Call. It sends a request to any endpoint of the Dynamic Mockups API through the same connection, so anything the API offers beyond Create a Mockup Render stays reachable. You write the request yourself from the Dynamic Mockups API documentation. The Make documentation for this app gives no numeric limit. If the render module alone covers your need, stick with it: it is simpler to set up.
05Should you use Make or n8n for Dynamic Mockups?
It depends on the tool you already run. In Make, Dynamic Mockups offers 2 modules, a render action and an API call, both on a standard app available from the Free plan. The same app often has an n8n node too, so the choice mostly comes down to where the rest of your automations live and which editor your team already knows. Neither tool is ranked above the other here; compare the two on your own scenario before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations