Resources · Make integration

Voice Partner Make integrationAutomate Voice Partner with Make.

Can Make hand a voice message to Voice Partner for you? Yes: the Voice Partner Make integration has 2 action modules and no trigger. This page is for teams who already use Voice Partner, and it walks you through the connection, a first scenario and each module.

Try the Voice Partner integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Voice Partner Make integration do?

The Voice Partner Make integration lets a Make scenario, the automation you build in Make, push work to your Voice Partner account without anyone opening it. Each scenario is a chain of modules, the bricks of the automation, and Voice Partner offers two of them: one to submit a voice message and one to reach any other part of its API.

Voice message after a form reply. A form tool such as the one in the 123FormBuilder Make integration starts the scenario, and Submit a voice message passes the reply details to Voice Partner. The form app does the watching, Voice Partner does the talking.

Voice message on a schedule. No other app needed: the scenario can start from its own clock, every 15 minutes by default, and hand a message to Voice Partner each time it runs.

Anything the listed module skips. Make an API Call reuses your connection to call any endpoint of the Voice Partner API, so a gap in the module list is not a dead end.

Know the limits before you start. Voice Partner has no trigger in Make, so a scenario never starts from something that happens inside Voice Partner. Make also says its documentation for this app is limited, since little public information exists about it; expect to discover field names in the module itself. Voice Partner often has an equivalent on n8n too, and the n8n vs Make comparison lays out how the two tools differ.

Connect

How do you connect Voice Partner to Make?

  1. 01

    Open the connection window

    Add a Voice Partner module to your scenario, then click Create a connection. A connection is your Voice Partner account linked to Make once, then reused by every Voice Partner module you add later.

  2. 02

    Name it so you can find it again

    Giving the connection a name is optional. Still, a clear label such as your team or account name saves guesswork once several people or several accounts share the same Make organization.

  3. 03

    Authorize and save

    Either approve Make on the Voice Partner page that opens, or paste the key Voice Partner gives you, depending on what the window asks. Then click Save and the module is ready to fill.

First scenario

Build your first Voice Partner scenario

GoalWhen a new entry lands in another app, Make submits a voice message to Voice Partner.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Voice Partner has no trigger, so the first module belongs to the app where the event happens.

  2. 02

    Pick the starting app

    Search that app by name, choose its trigger and click Create a connection. Fill its fields; once connected, Make lists what it can read there.

  3. 03

    Add Submit a voice message

    Click the + on the right of the first module, search Voice Partner and pick Submit a voice message. Connect your account as shown above.

  4. 04

    Map the incoming data

    Fill the fields the module shows by dragging values from the first module into them, so each message carries the details of the entry that started the run.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble on each module to read the bundles, the items that moved from one module to the next.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then flip the scenario on. From now on it runs without you.

Modules

What the Voice Partner modules do

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

Voice Partner1

Make an API Call

ActionIn the docs only

This module gives you access to the whole Voice Partner API through the connection you already created, so you can reach an endpoint that no ready-made module covers. You write the request yourself, so it takes a bit more care than a regular module.

When to use it
your process needs something from Voice Partner beyond submitting a voice message, and the API offers it.
Watch out
Make's documentation for this app is limited, so confirm with Voice Partner that the endpoint exists before you build around it.
Voice Partner2

Submit a voice message

ActionIn the docs only

Here is the module that turns an event in your other tools into a voice message handed to Voice Partner. Each bundle that reaches it counts as one operation, the unit Make measures on your plan, so a batch of ten entries means ten operations.

When to use it
a new order, form reply or record elsewhere should end with a message going out through Voice Partner.
Watch out
Make publishes no field list for it; open the module after connecting to see exactly what it asks for.
Need help

Need help automating Voice Partner with Make?

A person reads every message.

FAQ

Voice Partner and Make: common questions

01Is the Voice Partner Make integration free?
Yes, Voice Partner is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two 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) bring the interval down to 1 minute and remove the cap on active scenarios. This answer covers Make only; whatever Voice Partner charges for its own service is a separate matter to check with them.
02What do you need to connect Voice Partner to Make?
A Voice Partner account and a Make account are enough to start, since Make's documentation lists no other prerequisite. You add a Voice Partner module, click Create a connection, optionally name it, then either authorize Make on the Voice Partner page or paste the key the app gives you, and click Save. Keep in mind that Make describes its documentation for this app as limited, so if a key is requested, Voice Partner's own account settings or support are the place to find it.
03Can Voice Partner trigger a Make scenario in real time?
No, Voice Partner has no trigger module in Make, so nothing inside Voice Partner can start a scenario. You start it another way: put a trigger from another app first, instant if that app offers a webhook, or let the scenario run on its own schedule, every 15 minutes by default and down to 1 minute on paid plans. The Voice Partner modules then act as steps inside the flow rather than as its starting point.
04What if the Voice Partner module you need is missing in Make?
Use Make an API Call. With this module, any endpoint of the Voice Partner API can be called from the scenario, using the same connection as the other module, so the short list of 2 modules is not the ceiling. The catch is documentation: Make says it cannot fully document this app, so ask Voice Partner which endpoints exist and what they expect before you build. When the API does not cover your need either, another app in the same category may be a better fit.
05Should you pick Make or n8n for Voice Partner?
It depends on the tool your team already runs. In Make, Voice Partner comes with 2 action modules, including Make an API Call to reach the rest of its API, and it is available from the Free plan. The same app often has a node on n8n as well, so checking whether that node exists is the first step if your automations already live there. Neither choice is ranked here; the decision rests on where your other scenarios are and which editor your team knows.
Same platform

Other docs you might need on this stack.

Browse all integrations