Resources · Make integration

PiAPI/Sora Make integrationAutomate PiAPI/Sora with Make.

What if a line of text in one of your tools could become a video without you opening PiAPI/Sora? The PiAPI/Sora Make integration gives you 3 action modules and no trigger. This guide connects your account, then walks you through a first working scenario.

Try the PiAPI/Sora integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PiAPI/Sora Make integration let you automate?

The PiAPI/Sora Make integration links your PiAPI/Sora account to Make, so a scenario (the automation you build in Make, a chain of steps) can ask for a video generated from text and then pass that video along. Each step is a module, one brick of the scenario, and PiAPI/Sora offers three of them, all actions.

Videos from content your team already writes. A product description, a campaign brief or a script sits in another tool. A scenario picks it up and hands it to Generate a Video based on Text, so nobody has to paste prompts by hand.

A cleaner file before it goes further. When a video you work with carries a watermark, Remove Video Watermark handles that step inside the same scenario, instead of a separate manual pass.

Everything the list does not cover. Make an API Call reaches any endpoint of the PiAPI/Sora API with the connection you already set up. It is the way out when the two ready-made modules stop short.

What Make does not do here: PiAPI/Sora has no trigger, so nothing on the PiAPI/Sora side can start a scenario. The start comes from another app or from the schedule you set in Make. The Make documentation for this app also flags its own content as AI-generated, so check important details with PiAPI/Sora directly. For a broader look at the platform, read our Make review; if you are weighing tools, n8n vs Make lays out the criteria.

Connect

How do you connect PiAPI/Sora to Make?

  1. 01

    Generate your API key in PiAPI/Sora

    You need an active PiAPI/Sora account. Log in, open the workspace dashboard, go to the API key section and click Generate. Copy the key that appears on screen: Make will ask for it in a moment.

  2. 02

    Add a module and open the connection window

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps once you have several accounts. Paste the API key you copied, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with PiAPI/Sora

GoalWhen new text shows up in another app, Make sends it to PiAPI/Sora and gets a video back.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since PiAPI/Sora has no trigger, pick the app that holds your text as the first module.

  2. 02

    Set up the starting module

    Connect that other app and fill its fields. Each new item it finds becomes a bundle: one piece of data, here one text, passed on to the next module.

  3. 03

    Add the video module

    Click the + on the right, search for PiAPI/Sora and pick Generate a Video based on Text. Use your connection, then map the text from the first module into it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can see what PiAPI/Sora sent back before going further.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; on the Free plan that is also the shortest interval. Then switch the scenario on.

Modules

What can PiAPI/Sora do in Make?

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

PiAPI/Sora1

Generate a Video based on Text

ActionIn the docs only

Hand this module a piece of text and it asks PiAPI/Sora to produce a video from it, right inside your scenario. It is the core of the integration and the module most scenarios here are built around.

When to use it
a script or product description lands in another tool and you want a video draft without copying anything by hand.
Watch out
each run of the module counts as one operation on your Make plan, so test with Run once before letting a busy source feed it.
PiAPI/Sora2

Make an API Call

ActionIn the docs only

You get direct access to any endpoint of the PiAPI/Sora API, using the same connection as the other modules, without setting up authentication again. Think of it as the spare key for what the two ready-made modules do not offer.

When to use it
the PiAPI/Sora documentation describes a request you need and no dedicated module exists for it.
Watch out
you write the request yourself, so keep the vendor documentation open while you set it up.
PiAPI/Sora3

Remove Video Watermark

ActionIn the docs only

Removing the watermark from a video becomes one more step of the scenario instead of a separate job you do afterwards. The file can then move on to wherever it needs to go next.

When to use it
a video in your flow carries a watermark and the next module should receive the clean version.
Watch out
the Make documentation for this app is marked as AI-generated, so confirm on the PiAPI/Sora side what this module accepts.
Need help

Need help automating PiAPI/Sora with Make?

A person reads every message.

FAQ

PiAPI/Sora and Make: frequently asked questions

01Is the PiAPI/Sora Make integration free?
Yes on the Make side: PiAPI/Sora is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and raise the execution time to 40 minutes. PiAPI/Sora itself is a separate account: its subscription is described on its own pricing page, not by Make.
02What do you need to connect PiAPI/Sora to Make?
You need an active PiAPI/Sora account and an API key. Log in to PiAPI/Sora, go to the workspace dashboard, open the API key section, click Generate and copy the key. In Make, add a PiAPI/Sora module, click Create a connection, give it a name if you like and paste the key. That connection is then reused by every PiAPI/Sora module in your scenarios. If the key is refused, generate a new one in the workspace dashboard and paste it again.
03Can a PiAPI/Sora scenario in Make start on its own?
Not from PiAPI/Sora: the app has no trigger, only three actions. Your scenario has to start somewhere else. Two options: put a module from another app first, for example the tool where your scripts or descriptions are written, or rely on the schedule of the first module, which checks every 15 minutes by default. Then place Generate a Video based on Text after it and map the text across. Test the chain with Run once before switching the scenario on.
04What if the PiAPI/Sora module you need is missing in Make?
Use Make an API Call. It is included for this app and can call any endpoint of the PiAPI/Sora API with the same connection, so a feature the two dedicated modules skip is still reachable. Keep the PiAPI/Sora documentation at hand while you build the request. The Make documentation for this app is labeled as AI-generated content, so for anything that matters, check the vendor documentation or ask PiAPI/Sora. Test that request with Run once before you rely on it.
05Should you use Make or n8n for PiAPI/Sora?
It depends on what you check. On Make, PiAPI/Sora comes with 3 action modules, including Make an API Call, and no trigger, so you know exactly what is ready to use. The same app often has an n8n node as well, so compare what each tool offers for PiAPI/Sora before picking. If your other automations already run on one of them, keeping PiAPI/Sora there is usually the simplest path. The comparison page linked above goes through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations