Resources · Make integration

Motionlab Make integrationAutomate Motionlab with Make.

Can Make create your Motionlab videos while you work on something else? The Motionlab Make integration gives you 8 action modules, for videos, campaigns and status checks. This guide shows how to link your account and build a first scenario step by step.

Try the Motionlab integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Motionlab Make integration do for you?

The Motionlab Make integration links your Motionlab account to Make, so a scenario (the automation you build, a chain of steps) can ask Motionlab for a video and then check on it. Each step is a module, one brick of the scenario. Motionlab offers 8 of them, all actions, and no trigger.

Video on demand. A form, a CRM or a spreadsheet in another app starts the scenario, and Create a New Video sends the request to Motionlab with the data it received. When the request needs a body you shape yourself, Create a Video with Custom Body is the one to pick.

Follow-up on each video. Get a Video Creation Status tells the scenario where a video stands, and Get a Created Video Info brings back the details of a finished one, ready to pass to the next app.

Campaign reporting. Get a Campaign Overview and Get a Campaign Parameters read what a campaign holds, so another app can store or share it.

Know the limits before you build. Motionlab has no trigger in Make, so something else has to start the scenario. The official doc lists the modules without describing them, and it warns that its own text is AI-generated and may contain mistakes. Test each module with Run once before you rely on it. The Make troubleshooting guide helps when a run fails.

Many apps also have an n8n node. If you are weighing the two tools, read n8n vs Make, and see Make pricing for what each plan allows.

Connect

How do you connect Motionlab to Make?

  1. 01

    Copy your Motionlab keys

    You need an active Motionlab account, a campaign key and an API key. In Motionlab, open the Campaigns dashboard, click the campaign name, then the Launch step in the detail panel. The API key is shown there.

  2. 02

    Add a Motionlab module

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

  3. 03

    Paste the credentials

    Give the connection a clear name in Connection name if you like, it is optional. Then paste the credentials copied from Motionlab, or follow the instructions on screen, and save.

First scenario

Build your first scenario with Motionlab

GoalWhen new data lands in another app, Make asks Motionlab for a video and then checks how its creation is going.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Motionlab has no trigger, start with the app that holds your data, such as a form or a sheet.

  2. 02

    Add Create a New Video

    Click the + to the right of that first module, search for Motionlab and pick Create a New Video. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the incoming data

    Fill the module fields with data from the first module. Each bundle, one item passed from one module to the next, becomes one video request.

  4. 04

    Check the status

    Add Get a Video Creation Status after it and map the video returned by the previous module, so the scenario knows where the creation stands.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which is the best way to see what Motionlab really sends back.

  6. 06

    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 plan.

Modules

What each Motionlab module does

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

Motionlab1

Create a New Video

ActionIn the docs only

This is the module that gets a video started: it sends a creation request to Motionlab from the data your scenario carries. The doc gives no description, so check its fields in the editor.

When to use it
a new lead or row in another app should lead to a Motionlab video without anyone opening Motionlab.
Watch out
every bundle that reaches it creates a request, so filter upstream if only some items deserve a video.
Motionlab2

Create a Video with Custom Body

ActionIn the docs only

You get more control over the request here, since the name says you write the body of the video creation call yourself. Pick it over Create a New Video when the standard fields do not cover what you need.

When to use it
your video request needs a structure the simpler module does not offer.
Watch out
the doc does not describe the expected body, so test with Run once before switching the scenario on.
Motionlab3

Get a Campaign Overview

ActionIn the docs only

Reading a campaign summary into your scenario is what this module is for, so you can pass it to a sheet, a chat or a report in another app. It creates nothing in Motionlab.

When to use it
a teammate asks where a campaign stands and you want the answer delivered by Make instead of a manual export.
Watch out
the doc does not list what the overview contains; run it once and read the bundle before mapping anything.
Motionlab4

Get a Campaign Parameters

ActionIn the docs only

Use it to pull the settings of a campaign into the scenario, as opposed to its overview. That makes it the right source when a later step has to reuse how the campaign is configured.

When to use it
before creating videos, to check or copy the parameters of the campaign you are working with.
Watch out
the parameters available depend on your campaign; the doc names none, so look at what Run once returns.
Motionlab5

Get a Created Video Info

ActionIn the docs only

Once a video exists, this module brings its details back into Make, so the next app can store them, send them or attach them to a contact. It reads, it does not change the video.

When to use it
after the creation is finished and you want to hand the result to a CRM, an email tool or a sheet.
Watch out
the doc does not say what comes back for a video still in progress, so check its status with the module below first.
Motionlab6

Get a Video Creation Status

ActionIn the docs only

Knowing whether a video is still in progress or ready is the whole point of this module. It answers for one video, which lets the scenario decide what to do next.

When to use it
right after Create a New Video, or in a separate scenario that checks pending videos before sending them on.
Watch out
the doc does not list the possible status values, so read them in a Run once test before you build a filter on them.
Motionlab7

Get an API Status

ActionIn the docs only

A quick health check: judging by its name, this module asks Motionlab whether its API is answering, which helps when a scenario fails and you need to know which side is at fault.

When to use it
at the start of a scenario that creates videos, so a failed check can stop the run early instead of sending requests into the void.
Watch out
it says nothing about your campaign or your keys; a working API does not prove your connection is right.
Motionlab8

Make an API Call

ActionIn the docs only

When none of the seven other modules fits, this one lets you call any endpoint of the Motionlab API from the scenario, with the same connection and no extra login.

When to use it
you found an endpoint in the Motionlab API documentation that the listed modules do not cover.
Watch out
you write the request yourself, so you need the API reference from Motionlab; this page cannot tell you which endpoints exist.
Need help

Need help automating Motionlab with Make?

A person reads every message.

FAQ

Motionlab and Make: frequent questions

01Is the Motionlab Make integration free?
Yes, on the Make side. Motionlab is a standard app, so its modules are available 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) lower the interval to 1 minute and allow 40 minutes of execution. Your Motionlab subscription is separate: check the Motionlab pricing page for it.
02What do you need to connect Motionlab to Make?
You need an active Motionlab account, a campaign key and an API key. The API key sits in Motionlab: open the Campaigns dashboard, click the campaign name, then the Launch step of the detail panel, and copy the key shown there. In Make, add a Motionlab module, click Create a connection, optionally name it, then paste the credentials. The connection is created once and reused by all 8 Motionlab modules in your scenarios.
03How does a Motionlab scenario start in Make without a trigger?
It starts from something else, because Motionlab has no trigger module in Make. You have two options. Put another app first, for example the form, CRM or sheet whose data should become a video, and let its trigger start the flow. Or run the scenario on a schedule set on its first module, every 15 minutes by default, with a minimum of 15 minutes on the Free plan and 1 minute on paid plans. Either way, the Motionlab modules come after that first step.
04What if a Motionlab module is missing in Make?
Use Make an API Call. It calls any endpoint of the Motionlab API with the connection you already have, so you are not limited to the 8 listed modules. You will need the Motionlab API reference to write the request. Keep in mind that the Make doc for this app lists module names without descriptions and states that its content is AI-generated and may contain mistakes. When a detail matters, confirm it with Motionlab directly or test it with Run once.
05Should you use Make or n8n for Motionlab?
It depends on the tool you already run. In Make, Motionlab offers 8 action modules, including Make an API Call for anything they miss, and it works from the Free plan. Many apps also have an n8n node, so check whether one exists for Motionlab before choosing. If your other automations already live in Make, keeping Motionlab there means one place to build, test and watch your scenarios. Compare the modules each tool offers for your case, not the tool names.
Same platform

Other docs you might need on this stack.

Browse all integrations