Resources · Make integration

PiAPI/DiffRhythm Make integrationAutomate PiAPI/DiffRhythm with Make.

Need audio produced from text without opening PiAPI/DiffRhythm each time? The PiAPI/DiffRhythm Make integration gives you 2 action modules and no trigger. This guide connects your account, builds a first scenario and shows where each module fits.

Try the PiAPI/DiffRhythm integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

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

The PiAPI/DiffRhythm Make integration lets a Make scenario (the automation you build, a chain of modules) send text to PiAPI/DiffRhythm and get audio back. A module is one brick of that chain. This app offers two, both actions, so something else has to start the run.

Audio from a form entry. A form tool starts the scenario, and Generate an Audio based on Text receives the text a visitor typed. The result travels on as a bundle, one item passed to the next module, ready to be stored or shared.

Audio from a spreadsheet row. Teams that draft scripts in a sheet can let Make pick up each new row on a schedule and send it to the same module. Every module run counts as one operation, the unit Make counts on your plan.

Anything the listed module misses. Make an API Call reaches any endpoint of the PiAPI/DiffRhythm API with the connection you already set up.

Know the limits before you start: Make itself says its documentation for this app is incomplete, because little public information exists about it. Test with Run once before relying on the output, and keep the Make troubleshooting guide close. To judge the platform as a whole, read the Make review; to weigh it against another tool, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect PiAPI/DiffRhythm to Make?

  1. 01

    Add a PiAPI/DiffRhythm module

    In your scenario, click the + and search for PiAPI/DiffRhythm. Pick Generate an Audio based on Text, then click Create a connection. A connection is your PiAPI/DiffRhythm account linked to Make once and reused by both modules.

  2. 02

    Name the connection

    This step is optional, but a clear name helps once you run several accounts or clients. Something like the project name makes the right connection easy to spot later in the module's dropdown list.

  3. 03

    Authorize and save

    Follow what the window asks: either authorize Make on the PiAPI/DiffRhythm page or paste the key the app gives you. Then click Save, and the module is ready for its fields.

First scenario

Your first scenario with PiAPI/DiffRhythm

GoalWhen new text lands in another app, Make sends it to PiAPI/DiffRhythm and gets audio back.

  1. 01

    Create the scenario

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

  2. 02

    Pick the starting app

    Search the app where the text lives, such as a form tool or a spreadsheet, choose its module and create its connection. Fill its fields so Make knows which source to read.

  3. 03

    Add the audio module

    Click the + on the right of that module and add Generate an Audio based on Text. Select your PiAPI/DiffRhythm connection, then map the text coming from the previous module into it.

  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 audio came back as expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on, each new text is sent to PiAPI/DiffRhythm without you stepping in.

Modules

What can PiAPI/DiffRhythm do in Make?

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

PiAPI/DiffRhythm1

Generate an Audio based on Text

ActionIn the docs only

You hand this action a piece of text and PiAPI/DiffRhythm returns audio built from it, as the module's name promises. It is the reason most people add this app to a scenario.

When to use it
right after the module that brings the text in, such as a new form entry or a fresh spreadsheet row.
Watch out
Make publishes no field list for this module, so run it once and read the output bundle before mapping it further.
PiAPI/DiffRhythm2

Make an API Call

ActionIn the docs only

This one opens the rest of the PiAPI/DiffRhythm API to your scenario, reusing the connection you already created, so no second login is needed.

When to use it
when the task you have in mind is not covered by Generate an Audio based on Text.
Watch out
you write the request yourself, and Make's documentation for this app is limited, so rely on the PiAPI/DiffRhythm API reference and test with Run once.
Need help

Need help automating PiAPI/DiffRhythm with Make?

A person reads every message.

FAQ

PiAPI/DiffRhythm and Make: common questions

01Is the PiAPI/DiffRhythm Make integration free?
Yes, on the Make side. PiAPI/DiffRhythm is a standard app, so it is available from the Free plan onward. That plan keeps 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 lift the cap on active scenarios. Make counts usage in credits, one operation per module run, so each generated audio uses at least one. What PiAPI/DiffRhythm itself charges is a separate matter, and this page does not cover it.
02What do you need to connect PiAPI/DiffRhythm to Make?
An active PiAPI/DiffRhythm account and a Make account. Make's documentation lists no specific prerequisite for this app. The connection follows Make's generic path: add a PiAPI/DiffRhythm module, click Create a connection, optionally give it a name, then either authorize Make on the app's page or paste the key the app provides, and click Save. Make itself notes that its documentation for this app is limited, so if a step does not match what you see, the account settings on the PiAPI/DiffRhythm side are the place to look.
03Can a PiAPI/DiffRhythm scenario start on its own?
Not from PiAPI/DiffRhythm itself, because the app has no trigger module in Make. Both of its modules are actions, so another element has to start the scenario. The simplest route is a module from the app that holds your text, such as a form or a spreadsheet, running on the scenario's schedule. A new scenario checks every 15 minutes by default, and the Free plan does not allow a shorter interval. If the source app offers an instant trigger, it calls Make through a webhook as soon as something happens, and PiAPI/DiffRhythm then runs right after it.
04What if the PiAPI/DiffRhythm module you need is missing?
Use Make an API Call. With this module, any endpoint of the PiAPI/DiffRhythm API can be called from your scenario using the connection you already created, which covers whatever Generate an Audio based on Text does not. You write the request yourself, so you need the app's API reference at hand. Keep in mind that Make describes its own documentation for this app as limited, due to scarce public information. Test every request with Run once and read the bundle that comes back before you switch the scenario on.
05Should you use Make or n8n for PiAPI/DiffRhythm?
It depends on the tool your team already runs. On Make, PiAPI/DiffRhythm offers two action modules plus the option to call its API directly, and the app works from the Free plan. The same app often has an n8n node too, so check that the one you need exists there before choosing. The decision then rests on your existing scenarios, the other apps you connect and who will maintain the automation. The comparison linked higher on this page lays out the criteria side by side, without ranking either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations