Resources · Make integration

PiAPI/Wanx Make integrationAutomate PiAPI/Wanx with Make.

Need videos generated from text or images without writing code? The PiAPI/Wanx Make integration gives you 6 action modules for video generation, plus a raw API call. This guide is for makers new to Make: connect your key, build a first scenario, then pick the right module.

Try the PiAPI/Wanx integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the PiAPI/Wanx Make integration?

The PiAPI/Wanx Make integration lets a Make scenario, the automation you build as a chain of modules, ask PiAPI/Wanx for a video and pass the result to your other tools. A module is one brick of that chain, and every PiAPI/Wanx module here is an action: it does something when the scenario reaches it.

Videos from written ideas. A marketer keeps short descriptions in a spreadsheet or a form. Each new entry flows into Create a Video based on Text, and the result goes wherever the team reviews drafts.

Motion from product stills. An online shop already has photos. Convert an Image to a Video or Generate Video based on Image takes a picture and hands back a clip you can file next to the product record.

A consistent look across clips. When a studio has trained a LoRA for its style, the two LoRA modules, Generate Video based on Text and LoRA and Generate Video based on Image and LoRA, bring that style into each request.

What the integration does not include: there is no trigger, so PiAPI/Wanx never starts a scenario by itself. Another app or a schedule starts it. For anything the listed modules miss, Make an API Call reaches the rest of the PiAPI API with the same connection. If you are weighing tools, read our n8n vs Make comparison, and check Make pricing before you scale. To learn the editor properly, the Make training starts from zero.

Connect

How do you connect PiAPI/Wanx to Make?

  1. 01

    Generate your PiAPI key

    Log in to the PiAPI workspace with your GitHub account, open the section labeled API key and click the button that generates a new key. Copy the key shown on screen: Make will ask for it in a moment.

  2. 02

    Add a module and open the connection

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, follow the on-screen instructions and save.

First scenario

Your first scenario with PiAPI/Wanx

GoalWhen a new idea lands in another app, Make sends it to PiAPI/Wanx and gets a video back.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since PiAPI/Wanx has no trigger, this first module comes from the app that holds your ideas.

  2. 02

    Add Create a Video based on Text

    Click the + on the right of that first module, search PiAPI/Wanx and pick Create a Video based on Text. Choose your connection or click Create a connection if it does not exist yet.

  3. 03

    Map the text in

    Fill the module fields and map the text coming from the first module. A bundle, one item passing from a module to the next, carries that text into PiAPI/Wanx.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and check what PiAPI/Wanx sent back.

  5. 05

    Schedule and switch on

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

Modules

What each PiAPI/Wanx module does

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

PiAPI/Wanx1

Convert an Image to a Video

ActionIn the docs only

Hands PiAPI/Wanx a still picture and gets a moving clip back, so a static asset becomes something you can post or file. Its name describes the plainest intent of the two image modules; the doc does not say more.

When to use it
a new product photo reaches your storage and you want a short animated version without opening another tool.
Watch out
the doc gives no field list for this module, so run it once and read the bundle before mapping its output further.
PiAPI/Wanx2

Create a Video based on Text

ActionIn the docs only

Turns a written description into a video, which means an idea typed in a form or a sheet can come out as a clip. No image is needed at the start.

When to use it
your team collects campaign ideas as text and wants a first visual draft for each one.
Watch out
the app offers a second text module, Generate Video based on Text and LoRA; pick that one only when a LoRA style must apply.
PiAPI/Wanx3

Generate Video based on Image

ActionIn the docs only

Produces a video that starts from an image you provide, giving you a second image entry point next to Convert an Image to a Video. The doc does not explain how the two differ.

When to use it
you want to compare outputs from both image modules on the same picture before settling on one.
Watch out
test both with Run once on one bundle each, since the doc offers no comparison to choose from.
PiAPI/Wanx4

Generate Video based on Image and LoRA

ActionIn the docs only

Combines a source image with a LoRA in one request, so the clip carries a style you already rely on. Use it when look and consistency matter as much as the picture itself.

When to use it
a brand with its own LoRA animates catalog shots and wants every clip to share that visual identity.
Watch out
the doc lists no LoRA options, so check in PiAPI/Wanx which ones your account can use.
PiAPI/Wanx5

Generate Video based on Text and LoRA

ActionIn the docs only

Starts from text and applies a LoRA, which gives you written ideas rendered in a recognizable style. It is the text module to reach for when the output must match a series.

When to use it
a content team writes episode descriptions and needs each resulting clip to look like the previous ones.
Watch out
without a LoRA to apply, Create a Video based on Text is the choice, since it needs no style to apply.
PiAPI/Wanx6

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the PiAPI/Wanx API from your scenario while reusing the same connection, so you are not limited to the five video modules above.

When to use it
the endpoint you need has no dedicated module in Make, and you know its path from the vendor documentation.
Watch out
you write the request yourself here, so keep the PiAPI/Wanx documentation open and test with Run once first.
Need help

Need help automating PiAPI/Wanx with Make?

A person reads every message.

FAQ

PiAPI/Wanx and Make: common questions

01Is the PiAPI/Wanx Make integration free?
Yes, on the Make side. PiAPI/Wanx 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 of execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits per month. Your PiAPI/Wanx account is a separate subscription: the vendor pricing page covers it.
02What do you need to connect PiAPI/Wanx to Make?
An active PiAPI/Wanx account and an API key. You create the key in the PiAPI workspace, which you log in to with GitHub: open the API key section, generate a new key and copy it. In Make, add a PiAPI/Wanx module, click Create a connection, give it a name if you like and paste the key. Every PiAPI/Wanx module in your scenarios then reuses that connection. Treat the key like a password: it sits in the connection, so keep it private and generate a new one in the workspace if it ever leaks.
03Can PiAPI/Wanx start a Make scenario in real time?
No. The app has no trigger module, scheduled or instant, so nothing in PiAPI/Wanx can start a scenario on its own. Start the scenario with a trigger from another app, such as a form or a spreadsheet, or with a schedule on the first module, every 15 minutes by default. The PiAPI/Wanx action then runs each time a bundle reaches it. Once the scenario is switched on, every run uses operations on your plan, one for each module that processes a bundle.
04What if a PiAPI/Wanx module is missing in Make?
Use Make an API Call. It reaches any endpoint of the PiAPI/Wanx API with the connection you already set up, which covers whatever the five video modules leave out. Keep in mind the doc itself carries a warning: it is AI-generated from the vendor documentation and may contain mistakes, so confirm important details with PiAPI/Wanx directly before relying on them. Make an API Call sits in the scenario like any other module, so you test it with Run once and read the returned bundle the same way.
05Should you use Make or n8n for PiAPI/Wanx?
It depends on where the rest of your automations already live. On Make, PiAPI/Wanx comes with 6 modules, including Make an API Call for any other endpoint, and it runs from the Free plan. Many apps also have an n8n node, so check whether PiAPI/Wanx does before comparing. The deciding criteria are the tool your team knows and the modules each side offers, not a ranking. A practical way to decide: start where your first step lives, the form or spreadsheet that feeds ideas, since PiAPI/Wanx always needs another app or a schedule to begin.
Same platform

Other docs you might need on this stack.

Browse all integrations