Resources · Make integration

Creatomate Make integrationAutomate Creatomate with Make.

Can Make produce your Creatomate videos while you work on something else? The Creatomate Make integration gives you 4 modules: one instant trigger and three actions. This guide is for teams that already design templates in Creatomate and want each render to start, and land, on its own.

Try the Creatomate integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Creatomate Make integration let you automate?

The integration links your Creatomate account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. With it, Make can ask Creatomate to render a video, an image or a GIF, and react when a render comes out, without you opening either tool.

Product visuals from a template. A marketing team keeps one template per format in Creatomate. When a new product lands in its catalog app, Render a Template fills the template with that product's data and produces the visual.

Fully custom renders. When no template fits, Render from JSON lets you describe the whole composition as JSON data built earlier in the scenario, so each output can differ from the last one.

Delivery the moment a file is ready. Watch Render is an instant trigger: Creatomate calls Make as soon as a new video, image or GIF exists, and the next module can store it or share it with your team.

What the listed modules do not cover goes through Make an API Call, which reaches the rest of the Creatomate API with the same connection. The same app often has an n8n node too; the n8n vs Make comparison helps you pick a tool. To learn the editor itself, see our Make training, and check Make pricing before you scale up.

Connect

How do you connect your Creatomate account to Make?

  1. 01

    Copy your Creatomate API key

    In Creatomate, open your account dashboard, select the project your renders belong to, and copy the API key shown for that project. Each project has its own key, so pick the right one before copying.

  2. 02

    Add a Creatomate module in Make

    In your scenario, add any Creatomate module and click Create a connection. A connection is your Creatomate account linked to Make once, then reused by every Creatomate module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name such as the project name helps later. Paste the API key you copied, or follow the instructions Make shows on screen, and save.

First scenario

Your first scenario with Creatomate

GoalWhen a new item appears in the app your team already uses, Make asks Creatomate to render its visual from a template.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Start from your source app

    Pick the module of the app where new products or articles appear, and click Create a connection for that app. This module decides when the scenario starts.

  3. 03

    Add Render a Template

    Click the + on its right, search for Creatomate and choose Render a Template. Create the connection with your project's API key, then map the incoming data into the template.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundle it received: a bundle is one item passing from a module to the next, here one product and then one render.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default when it is a scheduled trigger, then switch the scenario on so each new item gets its visual.

Triggers

What can start a Creatomate scenario?

1 module starts a scenario when something happens in Creatomate. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Creatomate as soon as it happens.

Creatomate1Watch Render

Watch Render

Instant trigger

In Make“Watches for a new video, image, or GIF”

Watch Render starts your scenario each time Creatomate produces a new video, image or GIF, so the finished file moves on without anyone checking the dashboard. Pair it with a render module in another scenario, and each file you order comes back to you without a manual download.

How it fires
instant, Creatomate calls Make through a webhook as soon as the render exists, with no waiting for a schedule.
When to use it
you want each finished clip saved to shared storage or sent to the person who asked for it.
Watch out
set it up with Create a webhook first, then Create a connection, or the trigger never receives anything.
Modules

What Creatomate modules are available in Make?

Creatomate gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Creatomate1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives you access to any endpoint of the Creatomate API, reusing the connection you already created, so you are not stuck when a feature has no dedicated module.

When to use it
the three other modules cannot do what you need and the Creatomate API documentation describes the call.
Watch out
you write the request yourself, so read the vendor docs before running it on real projects.
Creatomate2

Render a Template

Action

In Make“Creates a video, image, or GIF based on a template.”

Render a Template turns one of your Creatomate templates into a finished video, image or GIF, filled with data coming from earlier modules. You design the layout once and Make handles every new version.

When to use it
a new listing, product or article appears in another app and needs its own visual in a format you have already designed.
Watch out
each render is one operation, the unit Make counts on your plan.
Creatomate3

Render from JSON

Action

In Make“Creates a video, image, or GIF based on JSON data.”

Render from JSON builds a video, image or GIF from a JSON description instead of a saved template, which leaves room for layouts that change from one render to the next.

When to use it
the number of scenes or elements depends on the data, and a fixed template would be too rigid.
Watch out
this page does not describe the JSON format, so rely on Creatomate's own documentation to structure the data you send.
Need help

Need help automating Creatomate with Make?

A person reads every message.

FAQ

Creatomate and Make: frequent questions

01Is the Creatomate Make integration free?
Yes, on the Make side. Creatomate is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits per month. You still need your own Creatomate account and subscription, which Make does not cover.
02What do you need to connect Creatomate to Make?
An active Creatomate account and the API key of the project you want to render from. You find it on your Creatomate account dashboard: select the project, then copy the key displayed for it. In Make, add a Creatomate module, click Create a connection, give it a name if you like and paste the key. For the Watch Render trigger, click Create a webhook before creating the connection. Once saved, the connection serves every Creatomate module in your scenarios.
03Does the Creatomate trigger in Make react in real time?
Yes. Watch Render is an instant trigger: Creatomate calls Make through a webhook as soon as a new video, image or GIF is ready, so the scenario starts right away instead of waiting for the next scheduled check. The default schedule of every 15 minutes applies to scheduled triggers, not to this one. If you start your scenario from another app instead, its first module sets the timing, and the render modules follow it.
04What if a Creatomate module is missing in Make?
Use Make an API Call. It sends any request the Creatomate API accepts, with the connection you already have, so actions without a dedicated module stay within reach. You need to know the endpoint and the data it expects, which the Creatomate documentation describes. The Make documentation for this app notes that its content is AI-generated from the vendor docs and may contain mistakes, so check important details with Creatomate directly before relying on them.
05Should you use Make or n8n for Creatomate?
It depends on the tool your team already works in. Creatomate has 4 modules in Make, including an instant trigger and Make an API Call for everything else, and the same app often has an n8n node as well. Choose Make if you want to build visually with ready modules and the connection flow described on this page. If your automations already live in n8n, check its Creatomate node there before moving anything.
Same platform

Other docs you might need on this stack.

Browse all integrations