Resources · Make integration

PiAPI/Veo Make integrationAutomate PiAPI/Veo with Make.

What if every prompt your team writes could come back as a video, without anyone opening PiAPI? The PiAPI/Veo Make integration gives you 3 action modules: text to video, image to video, and a raw API call. Here you link your key and build a first scenario that works.

Try the PiAPI/Veo integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PiAPI/Veo Make integration do?

The PiAPI/Veo Make integration lets a Make scenario ask PiAPI/Veo for a video. A scenario is the automation you build in Make, a chain of modules; a module is one brick of that chain. Here, every brick is an action: you hand it a text or an image, and PiAPI/Veo generates the video for you.

Text prompts that become clips. A marketer drafts short prompts in a spreadsheet or a form. The module Generate a Video based on Text picks up each prompt and requests the video, so nobody copies text into PiAPI by hand.

Product photos that start to move. An online shop already has product images. Generate a Video based on Image takes one image as its starting point and asks Veo to animate it, which suits a catalog that grows item by item.

Anything else the API offers. When neither module covers your need, Make an API Call reaches another endpoint of the PiAPI API with the same connection.

Keep in mind what the app does not bring: it has no trigger, so PiAPI/Veo never starts a scenario on its own. Something else has to kick it off, another app or a schedule. The Make documentation for this app is also marked as AI-generated, so double-check anything important with PiAPI directly. The same app often exists as an n8n node too; the n8n vs Make comparison helps you choose. To see what Make costs on your side, open Make pricing, and if a run fails, Make troubleshooting is the place to start.

Connect

How do you connect PiAPI/Veo to Make?

  1. 01

    Generate your API key

    You need an active PiAPI/Veo account first. In the PiAPI workspace, click your profile, open the API key section, press Generate and copy the key shown on screen. Keep it somewhere safe for the next step.

  2. 02

    Open the connection window

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the API key you copied, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with PiAPI/Veo

GoalWhen a new prompt shows up in another app, Make sends it to PiAPI/Veo and gets a video generated from that text.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since PiAPI/Veo has no trigger, this first module comes from the app where your prompts live.

  2. 02

    Pick the source of your prompts

    Search that app by name, choose the module that reads your prompts and link its account. Each prompt it returns becomes a bundle, one item that flows to the next module.

  3. 03

    Add the Veo text module

    Click the + on the right of the first module, search PiAPI/Veo and pick Generate a Video based on Text. Create the connection with your API key, then map the prompt from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and check that the prompt reached PiAPI/Veo.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Every module run counts as one operation, which is what Make bills against your plan.

Modules

What can the PiAPI/Veo modules do?

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

PiAPI/Veo1

Generate a Video based on Image

ActionIn the docs only

Hand this module a picture and you get a video request built from it, so a still image turns into moving footage without leaving your scenario.

When to use it
your starting material is visual, such as a product shot or a design that another module has just delivered, and you want it animated rather than described.
Watch out
Make lists what it can read only once the connection exists, so create the connection before you try to map an image into the module.
PiAPI/Veo2

Generate a Video based on Text

ActionIn the docs only

You write a prompt, this module asks Veo for a clip that matches it, so a written idea becomes a video request without any copy and paste.

When to use it
your ideas start as words, for example a script line typed in a form or a row added to a sheet, and you have no image to begin with.
Watch out
each call is one operation on your Make plan, so run the scenario once on a single prompt before letting it loop over a long list.
PiAPI/Veo3

Make an API Call

ActionIn the docs only

This one opens the rest of the PiAPI API to your scenario: any endpoint the two video modules do not cover can be called here, with the connection you already set up.

When to use it
you need a request that has no dedicated module, and you know which endpoint of the PiAPI documentation answers it.
Watch out
you build the request yourself, so keep the PiAPI API reference open and test it with Run once first.
Need help

Need help automating PiAPI/Veo with Make?

A person reads every message.

FAQ

PiAPI/Veo and Make: common questions

01Is the PiAPI/Veo Make integration free?
Yes on the Make side: PiAPI/Veo is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and allow 40 minutes of execution. PiAPI/Veo itself needs an active account and subscription, which its own pricing page covers.
02What do you need to connect PiAPI/Veo to Make?
An active PiAPI/Veo account and an API key. In the PiAPI workspace, click your profile, go to the API key section, press Generate and copy the key. Then, in Make, add a PiAPI/Veo module, click Create a connection, give it a name if you like and paste the key. That single connection serves all three modules of the app, so you set it up only once. If Make refuses the key later, generate a new one in the PiAPI workspace and paste it again.
03Can PiAPI/Veo trigger a Make scenario in real time?
No. PiAPI/Veo has no trigger module at all, so it cannot start a scenario by itself. The scenario begins with another app, for instance the form or sheet where your prompts land, or with a schedule on the first module, every 15 minutes by default. The Veo modules then run as actions further down the chain, once per bundle they receive. Before switching the scenario on, click Run once to check that each Veo module gets the text or image you expect.
04What if a PiAPI/Veo module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the PiAPI API with the connection you already created, so a request without its own module is still possible. You write that request yourself from the PiAPI documentation. Note also that the Make documentation for this app is flagged as AI-generated and may contain mistakes, so check important details with PiAPI/Veo directly. Test each custom request with Run once before activating the scenario, then read the bundles the module received.
05Should you use Make or n8n for PiAPI/Veo?
It depends on the tool your team already works in. On Make, PiAPI/Veo offers three action modules: text to video, image to video and a generic API call, and it runs from the Free plan. The same app often has an n8n node as well. Compare which modules each side exposes for your case before deciding; this page makes no claim about speed or price between the two. The n8n vs Make comparison, linked earlier on this page, sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations