Resources · Make integration

JSON2Video Make integrationAutomate JSON2Video with Make.

What if every new row of data came back as a finished video? The JSON2Video Make integration gives you 11 action modules to render movies, add subtitles and join clips. This guide shows how to link your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the JSON2Video Make integration let you do?

The JSON2Video Make integration connects your JSON2Video account to Make so a scenario (the automation you build in Make, a chain of modules) can order videos for you. Each module is one brick: here, all 11 are actions that create, subtitle, assemble or check a movie.

A listing video for each new property. A real estate team stores listings in a spreadsheet. A trigger from that tool starts the scenario, Create a Movie from my Template fills a template designed on JSON2Video.com, and Wait for a Movie to Render holds the next step until the file exists.

Subtitles on videos you already have. A course creator drops a recorded lesson somewhere Make can read. Add Automatic Subtitles to a Video transcribes the voice-over and adds captions to it, so the lesson works with the sound off.

One product clip out of several. An online shop keeps short clips per product. Concat a List of Videos with Background Audio joins them and lays music or a voice-over underneath.

Worth knowing before you start: JSON2Video has no trigger in Make, so something else has to start the scenario (another app or a schedule). The same video jobs can often be built in n8n too; the n8n vs Make comparison lays out the criteria. New to the editor? Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect JSON2Video to Make?

  1. 01

    Get your API key by email

    On the JSON2Video website, click Get your API Key, type your email address and click Send it to me!. The key lands in your inbox. Copy it, paste it into the field JSON2Video shows and click Confirm.

  2. 02

    Create the connection in Make

    In your scenario, add any JSON2Video module and click Create a connection. A connection is your JSON2Video account linked to Make once, then reused by every JSON2Video module. Give it a name in Connection name if you like, and paste the key into API Key.

  3. 03

    Save and approve access

    Click Save. If Make asks you to authenticate, sign in and confirm access. From there, every JSON2Video module in any scenario can pick this connection from the list instead of asking for the key again.

First scenario

Your first scenario: a video rendered from your template

GoalWhen new data arrives in another app, Make asks JSON2Video to render a movie from your template and waits until the video is ready.

  1. 01

    Create the scenario and its starting point

    Open Scenarios, create a new one and click the +. JSON2Video has no trigger, so pick the module of the app that holds your data, such as a form or a spreadsheet.

  2. 02

    Add the template module

    Click the + on the right, search for JSON2Video and choose Create a Movie from my Template. Select the connection you created, then the template you designed on JSON2Video.com.

  3. 03

    Map your data into the template

    Fill the module fields by mapping values from the first module into the spots your template leaves open. Each item that flows between modules is a bundle, so one new row gives one bundle and one movie.

  4. 04

    Wait for the render

    Add Wait for a Movie to Render after it and map the movie returned by the previous module. Any step you put after this one works with a finished video rather than a job still in progress.

  5. 05

    Test, then switch it on

    Click Run once and read the bundles each module received. When the output looks right, set the schedule on the first module (every 15 minutes by default) and switch the scenario on.

Modules

What each JSON2Video module does

JSON2Video gives you 11 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Toolbox

4 modules
JSON2Video1

Add Automatic Subtitles to a Video

Action

In MakeTranscribes a video or an audio input and adds subtitles to a video.

You get a subtitled video from either a video or a separate audio input: the module transcribes the sound and writes the captions onto the video.

When to use it
your narration lives in its own audio file, recorded apart from the footage, and you still want captions on the final clip.
Watch out
another module in the list carries the exact same name; this is the one that accepts audio input, so check the note below before picking.
JSON2Video2

Create Slideshow with Audio

Action

In MakeCreates a video slideshow from images or videos and adds a background audio

A handful of images or short videos comes back as one slideshow video with a background track playing under it.

When to use it
a new product or property arrives with a set of photos and no footage, and you want something that moves for social posts or a listing page.
Watch out
the result is a slideshow, not a designed layout; when you need your logo and fixed scenes, a template module is the closer fit.
JSON2Video3

Concat a List of Videos with Background Audio

Action

In MakeConcatenates a list of videos with the possibility to add a background music and voice over.

Several clips become a single video, played one after the other, with the option of background music and a voice-over on top.

When to use it
an intro, a product clip and an outro already exist as separate files and you want them stitched in the same order every time.
Watch out
a list is expected here, so if clips arrive as separate bundles, group them first.
JSON2Video4

Toolbox

Action

In MakeIncludes several video editing tools

This module gathers several video editing tools from JSON2Video behind one entry, handy when the job is a small edit rather than a full movie.

When to use it
none of the named modules fits the change you want and you would rather stay on a ready module than write an API request.
Watch out
the documentation does not detail which tools it includes; open the module in Make to see what it offers.

Basic

4 modules
JSON2Video5

Wait for a Movie to Render

Action

In MakeWaits for a movie to be rendered.

Your scenario pauses on this step until JSON2Video has finished rendering the movie, so the next module receives a real video and not a pending job.

When to use it
right after any module that creates a movie, whenever the following step sends, stores or posts the file.
Watch out
if you prefer to check later rather than wait, Check a Movie Status is the module for that.
JSON2Video6

Create a Movie from my Template

Action

In MakeCreates a new movie from one of your templates created on JSON2Video.com

One of the templates you designed on JSON2Video.com turns into a new movie, filled with the data your scenario maps into it.

When to use it
the layout is settled (logo, fonts, scenes) and only the text and pictures change from one video to the next, such as a listing or a product card.
Watch out
it only sees templates in your own account; for another template, use the Template ID module.
JSON2Video7

Create a Movie from a Template ID

Action

In MakeCreates a new movie from any template if you know the ID

Knowing a template's ID is enough to get a new movie from it, even when that template is not one you built yourself.

When to use it
a colleague or a client shares the ID of a template, or you switch between templates depending on the data, for example one layout per product family.
Watch out
Make cannot guess the ID; keep it in your data or type it into the module.
JSON2Video8

Check a Movie Status

Action

In MakeChecks your movie rendering status by providing your "project ID" and returns the video URL when the movie is ready.

Give it a movie's project ID and it tells you where the render stands, returning the video URL once the movie is ready.

When to use it
a separate scenario picks up movies ordered earlier and publishes the ones that are done, instead of holding the first scenario open.
Watch out
keep the project ID from the module that created the movie, since this check needs it.

Other

2 modules
JSON2Video9

Create a Movie from JSON

Action

In MakeCreates a new movie from the provided JSON

Here you describe the whole movie yourself in JSON (scenes, texts, media) and JSON2Video renders exactly that, without a saved template.

When to use it
the structure of the video changes with the data, for instance a variable number of scenes, and no single template can follow.
Watch out
this is the most technical module of the app; start from a template module if you have never written JSON.
JSON2Video10

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

This module lets you call any endpoint of the JSON2Video API from your scenario, reusing the connection you already set up.

When to use it
you need a JSON2Video feature that none of the 10 other modules covers and you are comfortable reading the API documentation.
Watch out
Make does not build the request for you here; you write it from the JSON2Video API documentation.

Other modules

1 module
JSON2Video11

Add Automatic Subtitles to a Video

Action

In MakeTranscribes a video's voice-over and adds automatic subtitles.

A video with a spoken voice-over comes out with automatic subtitles, generated from what the speaker says in it.

When to use it
the voice is already inside the video, as in a recorded webinar or a talking-head clip, and you just want captions added.
Watch out
it shares its name with the module in the Toolbox group; pick that one when your narration sits in a separate audio file.
Need help

Need help automating JSON2Video with Make?

A person reads every message.

FAQ

Questions about JSON2Video and Make

01Is the JSON2Video Make integration free?
Yes, on the Make side. JSON2Video is a standard app, 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 drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Each module run on one bundle is an operation, which is what Make counts on your plan. What JSON2Video itself charges for rendering is not covered here.
02What do you need to connect JSON2Video to Make?
A JSON2Video account and its API key. You request the key on the JSON2Video website with Get your API Key, and it arrives by email. In Make, add a JSON2Video module, click Create a connection, paste the key into the API Key field and click Save. If Make asks you to authenticate, confirm access. The connection is then reused by all 11 modules, so you do this once per account rather than once per scenario.
03Does JSON2Video have a trigger to start a Make scenario?
No. All 11 JSON2Video modules are actions, so the scenario has to start somewhere else. The usual choice is a trigger from the app that holds your data, such as a form, a spreadsheet or a CRM, placed as the first module. The other option is a schedule: set the clock on the first module and Make runs the scenario at that interval, every 15 minutes by default. In both cases JSON2Video steps in afterwards, receiving the data and returning a movie.
04What if a JSON2Video module is missing in Make?
Use Make an API Call. It is part of the JSON2Video app in Make and calls any endpoint of the JSON2Video API with the connection you already have, so a feature without its own module is still reachable. Before that, open the Toolbox module, which groups several editing tools. The documentation lists no numeric limit for this app, so the constraints you will meet are those of your Make plan, such as execution time and file size.
05Should you use Make or n8n for JSON2Video?
It depends on what you already run. On Make, JSON2Video comes with 11 ready modules, including Make an API Call, and works from the Free plan, which suits someone who wants to assemble a video workflow in the visual editor. Many apps also have an n8n node, so check whether one exists for JSON2Video and whether it covers the modules you need. If your other automations already live in one of the two tools, staying there is usually the simplest choice.