Fliz Logo
Sign upSign in

By the Fliz team · Updated November 13, 2026

Make.com video automation: generate AI videos in your Make scenarios

Make (formerly Integromat) is where many marketing and content teams build their automations, scenario by scenario, from social media content to faceless YouTube channels. Fliz brings video generation into those scenarios. From a text, an idea or a URL, Fliz produces a complete narrated video (AI script, one generated image per scene, voiceover in 32 languages, synced subtitles and music) and your scenario takes the MP4 to the next step: storage, approval, publishing. You can connect the two with the Fliz app for Make or with Make’s HTTP module and the Fliz REST API. This page shows both, with three scenarios you can build.

Create a video
Made with Fliz from the URL of a news article.

How to automate video creation with Make

  1. 1

    Get your Fliz API key

    Create a key at app.fliz.ai/api-keys. The REST API is included in every Fliz plan at no extra cost, and it is what both connection methods use.

  2. 2

    Connect Fliz to Make

    Install the Fliz app for Make through the invitation link on fliz.ai/automation, or call the Fliz REST API from Make’s HTTP module with your key as a Bearer token.

  3. 3

    Create the video, then handle the result

    One scenario sends the video request from your trigger (sheet row, RSS item, webhook). Because rendering takes 2 to 20 minutes, a second step picks up the finished video and publishes, stores or shares it.

Two ways to connect Fliz and Make

The Fliz app for Make is installed through the invitation link on the Fliz automation page rather than from Make’s public app directory, then connected with your API key. Once installed, its modules appear in the scenario editor like any other app.

The second way works in any Make account, with no installation: Make’s HTTP module (Make a request) calls the Fliz REST API directly. The OpenAPI specification at https://app.fliz.ai/api/openapi lists every endpoint and field, including the generation options: script style, language and voice, visual style, format, subtitles and music. Send your API key in an Authorization header as a Bearer token. The API accepts 300 requests per minute, far more than any video scenario needs.

How the asynchronous flow works in Make

A video is not ready when the create request returns. The API answers right away with a video_id, and rendering takes 2 to 20 minutes depending on the length and the options. A Make scenario has two clean ways to wait for it:

  • Webhook (recommended): add a webhook_url to the create request sent with the HTTP module, pointing to a Custom webhook in a second scenario. Fliz calls it once when the video finishes, with the video id, a status of succeeded or failed and, on success, the video URL. The call is made a single time with no retry.
  • Polling: in the same scenario, wait with a Sleep module (Make caps it at 300 seconds), get the video by its id, and check whether it has reached the complete step (the value is complete, not completed). Loop until it is, then continue.
  • Safety net: because the webhook is not retried, run a scheduled scenario that lists recent videos and catches any that finished without reaching you.

Faceless YouTube automation with Make

Many Make.com video automation projects aim at the same thing: a faceless YouTube channel, or faceless Shorts and Reels, produced with as little manual work as possible. The usual Make scenario chains an AI model for the script, an image generation service, a voiceover service, a rendering tool with a JSON template and a subtitles step. With Fliz, those steps collapse into one request: the AI script, the AI images in one of 63 visual styles, the voiceover in 32 languages, the subtitles and the music are generated together, and Make only handles the trigger and the publishing.

That makes the scenario shorter and easier to maintain, but it does not make a fully automated channel a good idea. Read the section on YouTube policies below before you let a scenario publish on its own.

Scenario 1: Google Sheets content calendar to TikTok

One of the scenarios shown on fliz.ai: each new row in a content calendar becomes a vertical video, published on TikTok once it is ready.

  • Trigger: Google Sheets, watch new rows, in a sheet with columns such as topic, script style, language and status.
  • Action: create the video with an HTTP request to the Fliz API, mapping the topic to the text, setting 9:16 and passing your Custom webhook URL as webhook_url. If you use the Fliz app instead, follow the video by polling as described above.
  • Action: Google Sheets, update the row with the video_id and a status of “rendering”.
  • Second scenario: Custom webhook receives the finished video, a filter keeps only succeeded, then the row is updated and the MP4 goes to TikTok through your publishing tool or scheduler module.

Scenario 2: RSS feed to Instagram Reels

For news sites and blogs: every new item in a feed becomes a short narrated video for Instagram.

  • Trigger: RSS, watch feed items, on your blog or a news source you have the right to summarize.
  • Action: create the video from the item URL with the news script style (social media tone) and 9:16. Fliz reads the page and writes the script from it.
  • Second scenario: Custom webhook, then a Router. On the succeeded branch, publish to Instagram through your scheduler. On the failed branch, send a Slack or email alert with the video id.

Scenario 3: a faceless YouTube channel with a daily series

For a faceless YouTube channel that publishes a series: every day at 3pm, a new children’s story is generated, reviewed and then published on YouTube by the automation.

  • Trigger: schedule the scenario to run every day at 3pm, reading the next topic from a sheet.
  • Action: create the video with the children’s story script style, a storybook visual style and 16:9 or 9:16.
  • Second scenario: Custom webhook, then email the video link to a reviewer and wait for approval in the sheet before the upload step runs.
  • Publishing: Make’s YouTube app or your scheduler uploads the approved MP4, with the title and description from the sheet.

Translate and duplicate videos from Make

The Fliz API can also translate or duplicate an existing video. Translation adapts the script to the new language and records it with a native voice, with captions to match. In a scenario, that turns one approved video into a set of language versions: iterate over a list of languages and send one translate request per language, each with the same webhook_url. Add a filter on the receiving side so the translated videos are not translated again when they finish.

Faceless YouTube automation and platform policies

Fliz creates the videos; it does not publish to YouTube, TikTok or Instagram itself. Your Make scenario or your scheduler does. That gives you control, and a responsibility: YouTube’s monetization policies exclude repetitive or mass-produced content, and a scenario that posts every generated video without a human look is the fastest way to produce it. Keep the topics yours, keep a review step, and publish what you would watch.

A faceless YouTube channel built on Make automation can work when each video brings something: your own research, a clear angle, a recurring format, accurate facts. Use the automation to save production time on the script, the voiceover, the AI images and the subtitles, and spend that time on the content itself.

Credits, operations and costs

API access is included in every Fliz plan. Videos created from Make use the same credits as in the app: a simple video uses 95 credits, and options such as motion cost extra. Plans cover about 10, 20, 50 or 100 videos per month. On the Make side, every module run counts as an operation, so a webhook-based flow uses fewer operations than a polling loop. Fliz is not free: new accounts get one free trial video in 720p with the Fliz watermark, enough to test a scenario before you scale it.

Questions

Is there a Fliz app for Make.com?

Yes. It is installed through an invitation link on fliz.ai/automation and connected with your Fliz API key. You can also use Make’s HTTP module with the Fliz REST API, in any Make account.

How does Make know when a Fliz video is ready?

Pass a webhook_url pointing to a Custom webhook in Make, and Fliz calls it once when the video finishes. Or poll the video by id until it reaches the complete step.

How long does a video take to generate?

Between 2 and 20 minutes, depending on the length and the options. Plan your scenario around that delay instead of waiting inside one run.

Can Make publish Fliz videos to YouTube, TikTok or Instagram?

Fliz does not publish itself. Your Make scenario hands the finished MP4 to a publishing module or a scheduler, ideally after a review step.

Do I need a paid Fliz plan to use the API with Make?

The API is included in every plan. A new account gets one free trial video in 720p with a watermark; after that, videos use credits from a paid plan.

Can I translate videos automatically with Make?

Yes. Send a translate request for each target language. The script is adapted and read by a native voice in one of 32 languages.

Add video to your Make scenarios

Create your API key, connect Fliz to Make, and turn your next sheet row, RSS item or product into a narrated video.

Make.com Video Automation: AI Videos in Scenarios | Fliz