Resources · Make integration

PiAPI/MMAudio Make integrationAutomate PiAPI/MMAudio with Make.

Can Make add a generated soundtrack to your videos on its own? The PiAPI/MMAudio Make integration gives you 2 action modules, one of them dedicated to creating audio from a video. This page shows content teams how to link the account and build a first working scenario.

Try the PiAPI/MMAudio integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PiAPI/MMAudio Make integration do?

The PiAPI/MMAudio Make integration lets a Make scenario, the automation you build in Make, send a video to PiAPI/MMAudio and get audio generated from it. It works through modules, the bricks of a scenario, and it has no trigger of its own: another app or a schedule starts the run.

Sound for every new product clip. An e-commerce team drops silent product videos into a storage app. A trigger from that app starts the scenario, and Generate an Audio from a Video produces the audio track, ready to be passed to the next module.

A backlog handled without manual uploads. A training studio keeps a list of lesson videos in a spreadsheet. The scenario runs on its schedule, reads each row as one bundle (one item moving between modules), and sends the video to PiAPI/MMAudio. Each module run on each bundle counts as one operation on your Make plan, so a long list costs more operations than a short one.

An endpoint the listed modules skip. When the PiAPI API offers something the dedicated module does not cover, Make an API Call reaches it with the same connection.

What Make does not do here: watch PiAPI/MMAudio for events. There is no trigger, so the start always comes from elsewhere. The official doc also warns that its own text is AI generated and may contain mistakes, so check key details with PiAPI. To weigh the platform itself, read the Make review, see the plans on Make pricing, or compare both tools in n8n vs Make.

Connect

How do you connect PiAPI/MMAudio to Make?

  1. 01

    Generate your API key in PiAPI

    Log in to PiAPI and open the workspace dashboard. In the API key section, click Generate, then copy the key shown on screen. Your account needs credits or an active subscription for the calls to go through.

  2. 02

    Add the module and open the connection

    In your scenario, add a PiAPI/MMAudio module and click Create a connection. A connection is your PiAPI account linked to Make once, then reused by both modules 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, confirm, and the module is ready to be filled.

First scenario

Your first scenario with PiAPI/MMAudio

GoalWhen a new video shows up in the app where your team stores clips, Make sends it to PiAPI/MMAudio and gets audio generated for it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your videos land and its trigger.

  2. 02

    Add the PiAPI/MMAudio action

    Click the + on the right of that first module, search for PiAPI/MMAudio and choose Generate an Audio from a Video. Select your connection or create it with your API key.

  3. 03

    Map the video

    Fill the module fields by mapping data from the first module, so each new video found upstream is the one PiAPI/MMAudio works on. Make shows the available values once a bundle exists.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received to confirm the audio request went out.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (the clock icon, every 15 minutes by default) and turn the scenario on. From then on, it runs without you.

Modules

What can PiAPI/MMAudio do in Make?

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

PiAPI/MMAudio1

Generate an Audio from a Video

ActionIn the docs only

You hand PiAPI/MMAudio a video and get back generated audio for it, without leaving your scenario. This is the reason most people install the app, and the module you place right after the step that delivers the video.

When to use it
a batch of silent clips for social posts needs sound before the editor picks them up.
Watch out
PiAPI requires credits on your account for these calls, so test with Run once on a single video before scheduling.
PiAPI/MMAudio2

Make an API Call

ActionIn the docs only

Here you reach any endpoint of the PiAPI API that the dedicated module leaves out, using the connection you already created. It is the fallback, not the starting point.

When to use it
the PiAPI documentation lists a request you need and Generate an Audio from a Video does not offer it.
Watch out
you write the request yourself, so keep the PiAPI API documentation open while you set it up.
Need help

Need help automating PiAPI/MMAudio with Make?

A person reads every message.

FAQ

PiAPI/MMAudio and Make: common questions

01Is the PiAPI/MMAudio Make integration free?
Yes on the Make side: PiAPI/MMAudio 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 per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and count usage in credits. PiAPI itself is separate: the doc requires an active PiAPI account with enough credits or a subscription, so the audio generation is billed on that side, according to PiAPI's own pricing page.
02What do you need to connect PiAPI/MMAudio to Make?
You need an active PiAPI account with credits or a subscription, plus an API key. Log in to PiAPI, open the workspace dashboard, go to the API key section, click Generate and copy the key. In Make, add a PiAPI/MMAudio module, click Create a connection, optionally give it a name, and paste the key. That single connection then serves both modules, Generate an Audio from a Video and Make an API Call, so you only set it up once per account.
03Does PiAPI/MMAudio trigger Make scenarios in real time?
No. The app has no trigger module, scheduled or instant, so PiAPI/MMAudio never starts a scenario by itself. You start it in one of two ways. Either a trigger from another app opens the flow, for example the storage tool where videos arrive, or the scenario runs on its own schedule, every 15 minutes by default, with a minimum of 15 minutes on the Free plan and 1 minute on paid plans. The PiAPI/MMAudio module then sits after that starting point as an action.
04What if a PiAPI/MMAudio module is missing in Make?
Use Make an API Call. It calls any endpoint of the PiAPI API through the connection you already have, so a request that Generate an Audio from a Video does not expose is still reachable from the same scenario. Keep in mind that the official Make doc for this app is AI generated and warns that it may contain mistakes. When a detail matters, such as what a request expects, check it in the PiAPI documentation or ask PiAPI directly before building on it.
05Should you use Make or n8n for PiAPI/MMAudio?
It depends on where your other automations already live. Many apps also exist as an n8n node, so check whether PiAPI/MMAudio does before deciding. On Make, you get 2 ready modules, a visual editor where you test with Run once, and a Free plan with 2 active scenarios. The better choice is the tool your team already runs, since the video source and the next steps are usually built there. The comparison page linked above goes through the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations