Resources · Make integration

Fliki - Text to Video Make integrationAutomate Fliki - Text to Video with Make.

Can Make turn your scripts into Fliki videos without a single copy and paste? Yes. The Fliki - Text to Video Make integration gives you 3 modules: one instant trigger and two actions. This page shows how to link your account and build a first working scenario.

Try the Fliki - Text to Video integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Fliki - Text to Video Make integration let you automate?

The Fliki - Text to Video Make integration links your paid Fliki account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. Fliki can start a scenario when a video finishes rendering, and a scenario can ask Fliki to create a new video.

Videos created from content you already write. A marketing team keeps its scripts in another app. Each new entry flows into Create a New Video, and Fliki starts the video without anyone opening it. This is the scenario built step by step further down.

A finished video that reaches the right people. Watch Completed Video Render fires as soon as Fliki is done, so a content manager can have the result sent to a chat channel, a spreadsheet or a project board through another app's module.

The Fliki features the ready-made modules skip. Make an API Call reaches any endpoint of the Fliki API with the same connection, which is how a developer covers the rest.

Two limits to know first. The connection needs a paid Fliki plan, standard or higher, and a Make key generated inside Fliki. On the Make side, the Free plan runs 2 active scenarios; the Make pricing page explains the paid tiers. The same app often has an n8n node too: n8n vs Make sets out how to choose, and Make training helps if scenarios are still new to you.

Connect

How do you connect Fliki to Make?

  1. 01

    Generate your Make key in Fliki

    Log in to Fliki and open the Automation tab. Click + Create Key, select Make, then Generate. Copy the value and keep it somewhere safe, since Make will ask for it in a moment.

  2. 02

    Add a Fliki module and open the connection

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

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like, paste your key into API key and click Save. If Fliki asks you to authenticate and confirm access, accept, and the connection is ready.

First scenario

Build your first scenario with Fliki

GoalWhen a new script lands in the app your team writes in, Make asks Fliki to create a new video from it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Start from the app that holds your scripts

    Search the app where your team writes, pick its module and link your account with Create a connection. Each new item it sends forward is a bundle: one piece of data passed to the next module.

  3. 03

    Add Create a New Video

    Click the + on the right of that module, search Fliki and choose Create a New Video. Select the connection you set up earlier.

  4. 04

    Map the script into the fields

    Fill the fields Make displays for the module. Click inside a field and pick values from the first module, so each new script feeds its own video instead of fixed text.

  5. 05

    Test with Run once

    Click Run once with a single test entry ready. Make runs the scenario one time and shows the bundles each module received, so you can confirm Fliki got the right content.

  6. 06

    Schedule and switch it on

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

Triggers

What can start a scenario from Fliki?

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

Fliki - Text to Video1Watch Completed Video Render

Watch Completed Video Render

Instant trigger

In Make“Triggers when a video render is completed.”

Watch Completed Video Render starts your scenario the moment Fliki finishes rendering a video, so the result can move on without anyone refreshing the Fliki dashboard. Each finished render reaches Make as one bundle, ready to be mapped into the next module.

How it fires
instant. Fliki calls Make through a webhook as soon as the render is done, which is the lightning badge you see on the module.
When to use it
your team queues videos in Fliki and wants each one passed to another tool the moment it is ready.
Watch out
on this module, click Create a webhook first and only then Create a connection, as the Make documentation asks for instant modules.
Modules

What can Make do in Fliki?

Fliki - Text to Video gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Fliki - Text to Video1

Create a New Video

Action

In Make“Creates a new video on Fliki.”

Create a New Video asks Fliki to produce a video from inside your scenario, so an idea stored in another app becomes a Fliki project with no manual copying. Make lists the fields to fill once the connection exists, and you map values from earlier modules into them.

When to use it
a new brief, article or product entry lands elsewhere and should turn into a video on its own.
Watch out
every bundle that reaches this module creates one video, so run your first test on a single item.
Fliki - Text to Video2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets your scenario reach any endpoint of the Fliki API, using the connection you already set up, which fills the gaps left by the two ready-made modules. You choose the endpoint and Make sends the request on your behalf.

When to use it
you need a Fliki feature that neither Create a New Video nor the render trigger covers.
Watch out
start with the ready-made modules and keep this one for what they cannot do, since you describe the request yourself.
Need help

Need help automating Fliki - Text to Video with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Fliki - Text to Video Make integration free?
Partly. On the Make side, Fliki is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid Make plans lower the interval to 1 minute and allow 40 minutes per run. On the Fliki side, the connection only works with an active paid account on the standard plan or above, so a free Fliki account is not enough to get started.
02What does it take to connect Fliki to Make?
You need an active, paid Fliki account on the standard plan or higher, plus a Make key created in Fliki. Open the Automation tab, click Create Key, pick Make and generate the key, then copy it. In Make, add a Fliki module, click Create a connection, paste the key into the API key field and save. If Fliki asks you to authenticate and confirm access, do it. For the instant trigger, click Create a webhook before creating the connection.
03Does the Fliki trigger react in real time?
Yes. Watch Completed Video Render is an instant trigger: Fliki calls Make through a webhook as soon as a render is completed, so the scenario starts right away instead of waiting for a polling interval. That makes it the right entry point when a finished video has to reach another app quickly. A scenario that opens on a scheduled module of another app follows its schedule instead, which is every 15 minutes by default on a new scenario.
04What if a Fliki module is missing in Make?
Use Make an API Call. This module exists for Fliki and can call any endpoint of the Fliki API with the same connection you already created, so a feature that has no ready-made module stays within reach. The Fliki documentation in Make gives no numbered limit for these modules. If a scenario still fails, the Make troubleshooting resources on this site walk through the usual checks, and the team behind this page can help you set it up.
05Make or n8n for Fliki: which one fits?
It depends on where your other automations already run. In Make, Fliki comes with three modules: an instant trigger for completed renders, an action that creates a video and Make an API Call for the rest, available from the Free plan. The same app often has an n8n node as well, so check what that node offers before you decide. Compare the modules each side gives you for Fliki and pick the tool that covers your scenario with the least workaround.
Same platform

Other docs you might need on this stack.

Browse all integrations