Resources · Make integration

PiAPI/Kling Make integrationAutomate PiAPI/Kling with Make.

Can Make produce Kling videos for you while you work on something else? The PiAPI/Kling Make integration gives you 8 action modules for AI video. This guide is for marketers and store owners: link your API key, build a first scenario, then pick the right module.

Try the PiAPI/Kling integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PiAPI/Kling Make integration do?

The PiAPI/Kling Make integration lets a Make scenario (the automation you build, a chain of modules) send video requests to Kling through your PiAPI account. Each module is one brick of that chain. Here all 8 are actions: they do something when the scenario reaches them, and none of them watches for events.

Short clips from written ideas. A social media team keeps its video ideas in another tool. The scenario picks each new idea and hands it to PiAPI/Generate a Video based on Text, so the clip exists without anyone opening Kling.

Product pages that show the garment worn. An online clothing shop can pass its product pictures to PiAPI/Create a Virtual Try on. Pair it with PiAPI/Generate a Video based on an Image when a still picture should start moving.

One presenter, several voice tracks. A training team that records a talking head once can send it through PiAPI/Create a Video through Lip Synchronization, the module whose name points at matching lips to audio.

Know the edges before you start. PiAPI/Kling has no trigger, so another app or a schedule has to start the scenario. The official doc also warns that its own text was written with AI help and may contain mistakes, so check anything that matters with PiAPI/Kling. The same app may also exist as an n8n node; the n8n vs Make comparison helps you choose, the Make pricing page explains operations, and the Make training covers scenario basics.

Connect

How do you connect PiAPI/Kling to Make?

  1. 01

    Get your API key

    You need an active PiAPI/Kling account and an API key. Log in to the PiAPI workspace with your GitHub account, open the API key section, click Generate, then copy the key that appears on screen.

  2. 02

    Add a PiAPI/Kling module

    In your Make scenario, add any PiAPI/Kling module and click Create a connection. A connection is your PiAPI/Kling account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from PiAPI/Kling, or follow the instructions Make shows on screen, and confirm. From then on, every PiAPI/Kling module in any of your scenarios can pick this connection from its list.

First scenario

Your first scenario with PiAPI/Kling

GoalWhen a new video idea lands in another app, Make asks PiAPI/Kling to turn that text into a video.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your video ideas live and its trigger: PiAPI/Kling has none, so this first module comes from another app.

  2. 02

    Add the Kling module

    Click the + on the right of that first module, search for PiAPI/Kling and choose PiAPI/Generate a Video based on Text. Select your connection, or click Create a connection.

  3. 03

    Map the idea into the module

    Fill the module fields. Where the text goes, map the idea from the first module instead of typing it, so each new bundle (one item passed along, here one idea) carries its own text.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bubble above each module to read the bundles it received and check that Kling got the right text.

  5. 05

    Schedule and switch on

    On the first module, set the schedule: a new scenario checks every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Modules

What can PiAPI/Kling do in Make?

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

PiAPI/Kling1

Make an API Call

ActionIn the docs only

Reach any endpoint of the PiAPI/Kling API from your scenario, with the connection you already set up. It covers whatever the seven named video modules leave out.

When to use it
the Kling feature you need has no dedicated module, and the API documentation of PiAPI/Kling shows the request to send.
Watch out
here you write the request yourself, so keep the vendor documentation open and test each change with Run once before switching the scenario on.
PiAPI/Kling2

PiAPI/Create a Video through Lip Synchronization

ActionIn the docs only

Get a video where the speaker's lips follow a soundtrack, which is what the module's name describes. Handy for anyone who wants several spoken versions without filming again.

When to use it
a training or support team has one presenter clip and a new voice track arrives from another app in the scenario.
Watch out
the doc gives no detail on accepted media, so run a single test with Run once before feeding it a batch.
PiAPI/Kling3

PiAPI/Create a Virtual Try on

ActionIn the docs only

Show a piece of clothing on a person without a photo shoot: the module name points at a virtual try-on generated by Kling. Store owners get a fitting preview straight from their product pictures.

When to use it
a new product is added to your shop app and you want a worn view ready for the listing.
Watch out
every product that passes through counts as one operation, meaning one run of the module on your Make plan.
PiAPI/Kling4

PiAPI/Extend a Video based on a Prompt

ActionIn the docs only

Make an existing clip last longer, guided by a prompt that says what should happen next. You keep the footage you like and add to it instead of starting over.

When to use it
a clip produced earlier in the scenario is good but ends too soon for the ad slot or post it was made for.
Watch out
map the video from the previous module rather than pasting it, otherwise every run extends the same clip.
PiAPI/Kling5

PiAPI/Generate a Video based on Elements

ActionIn the docs only

Build a clip from several separate pieces, the elements its name refers to, rather than from one picture or one sentence. Going by the name, it helps when you already hold the separate assets and want Kling to combine them.

When to use it
your assets already sit in a folder or a sheet, and the scenario can collect them before calling Kling.
Watch out
the doc lists no accepted element types, so confirm them in the PiAPI/Kling documentation first.
PiAPI/Kling6

PiAPI/Generate a Video based on Text

ActionIn the docs only

Turn a written description into a short video, with no image needed at the start. It is the simplest entry point into Kling from Make, and the one the first scenario on this page uses.

When to use it
ideas arrive as text, from a form, a message or a row, and each one should come back as a clip.
Watch out
a vague sentence gives a vague video, so map a well-written field rather than a raw title.
PiAPI/Kling7

PiAPI/Generate a Video based on an Image

ActionIn the docs only

Bring a still picture to life: you start from an image and receive an animated clip. Product shots, illustrations and event photos all become motion content with no editing work.

When to use it
a new image lands in cloud storage and your social team wants a moving version of it.
Watch out
on the Free plan Make handles files of up to 5 MB, so keep source pictures light.
PiAPI/Kling8

PiAPI/Generate a Video based on an Image with Effects

ActionIn the docs only

Animate a picture and add a visual effect on top, as the module name spells out. You get a more stylized clip than the plain image module gives, from the same kind of source.

When to use it
a campaign needs eye-catching teasers built from existing visuals, not a faithful animation.
Watch out
the doc names no effect list, so check the options offered in the module once your connection exists.
Need help

Need help automating PiAPI/Kling with Make?

A person reads every message.

FAQ

Questions about PiAPI/Kling and Make

01Is the PiAPI/Kling Make integration free?
Yes, on the Make side. PiAPI/Kling is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a shortest gap of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the gap down to 1 minute and count usage in credits, meaning operations, each month. Your PiAPI/Kling subscription is separate and is described on the PiAPI/Kling pricing page.
02What do you need to connect PiAPI/Kling to Make?
An active PiAPI/Kling account and an API key. You create the key in the PiAPI workspace, which you open by logging in with your GitHub account: go to the API key section, click Generate and copy the key shown on screen. Back in Make, add any PiAPI/Kling module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves every PiAPI/Kling module you add later.
03Can PiAPI/Kling start a Make scenario on its own?
No. PiAPI/Kling has no trigger module, only 8 actions, so it cannot tell Make that something happened. The scenario has to start elsewhere. Either the first module comes from another app, such as a form, a sheet or a storage service, or the scenario simply runs on its schedule. A new scenario runs every 15 minutes by default; the Free plan keeps at least 15 minutes between runs, while paid plans go down to 1 minute.
04What if the PiAPI/Kling module you need is missing in Make?
Use Make an API Call. This module reaches any endpoint of the PiAPI/Kling API with the connection you already have, so a Kling feature without its own module stays within reach. You write the request following the PiAPI/Kling API documentation. Also note that the official Make doc for this app says its text was generated with AI help and may contain mistakes, so confirm important details, such as accepted media, with PiAPI/Kling directly.
05Should you use Make or n8n for PiAPI/Kling?
It depends on where your other automations already live. On Make you get 8 modules for PiAPI/Kling, including Make an API Call for anything they do not cover, and you can start on the Free plan. The same app often has an n8n node too, so check whether it exists before deciding. Pick the tool your team already maintains and knows how to debug, since that matters more than any single app.
Same platform

Other docs you might need on this stack.

Browse all integrations