Resources · Make integration

Voyp Make integrationAutomate Voyp with Make.

Can Make handle your Voyp calls for you? The Voyp Make integration gives you 7 modules: 1 trigger, 5 actions and 1 search. This page is for people who know Voyp but are new to Make, and it walks you from the connection to a first working scenario.

Try the Voyp integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Voyp Make integration do?

The Voyp Make integration links your Voyp account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single step such as a trigger, an action or a search. With 7 Voyp modules, Make can pick up call details, place or end a call, and fetch past calls for your other tools.

Callback requests handled for you. When a prospect asks to be called back in another app, such as a form tool or a CRM, the Create a Call module can hand the request to Voyp, so nobody has to copy a phone number by hand.

A call log your team can actually read. Watch Call Details picks up call information on the scenario's schedule, and Get a Call fetches the details of one call so a later module can store it where your sales or support team works.

Cleanup on your terms. Search Calls returns the calls that match what you ask for, and Delete a Call removes the ones you no longer need to keep. For anything the six named modules leave out, Make an API Call reaches the rest of the Voyp API with the same connection.

One honest limit: Make's own documentation for Voyp is thin, since the app publishes little public information. The field names you will see come from the editor once your account is connected, not from this page. If you are still learning the editor, Make training covers the basics, Make troubleshooting helps when a run fails, and n8n vs Make lays out how the two tools differ.

Connect

How do you connect Voyp to Make?

  1. 01

    Add a Voyp module

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

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when several accounts exist. Then authorize Make on the Voyp page that opens, or paste the key Voyp gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read your Voyp account and fill its lists, which is the quickest sign that the connection works.

First scenario

Your first scenario with Voyp

GoalWhen someone requests a callback in another app, Make asks Voyp to place the call.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This first module is the trigger that starts every run.

  2. 02

    Pick the source of the request

    Search for the app where callback requests arrive, such as your form tool or CRM, pick its trigger and connect it. Each request it sends on becomes a bundle, one item passed to the next module.

  3. 03

    Add Create a Call

    Click the + on the right, search for Voyp and choose Create a Call. Connect your account, then map the phone number from the previous module into the matching field.

  4. 04

    Test with Run once

    Send a test request, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the number before a real call goes out.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What starts a Voyp scenario

1 module starts a scenario when something happens in Voyp. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Voyp as soon as it happens.

Voyp1Watch Call Details

Watch Call Details

triggerIn the docs only

Watch Call Details gives your scenario a steady feed of Voyp call information, so what happens on the phone can reach the rest of your stack without anyone retyping it. Each call it finds becomes a bundle for the next module.

How it fires
scheduled. Make checks Voyp on the scenario's schedule, every 15 minutes by default, and never faster than 15 minutes on the Free plan.
When to use it
you want call details to land in a CRM record or a shared sheet without anyone copying them.
Watch out
the documentation does not describe which details it returns, so run it once and read the bundle before you map anything.
Modules

Everything Voyp can do in Make

Voyp gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Voyp1

Create a Call

ActionIn the docs only

Create a Call turns a request from another tool into an actual Voyp call, which saves someone from dialing the number by hand. It is the module to reach for when a scenario should start a conversation.

When to use it
a lead asks for a callback in a form and you want Voyp to handle it.
Watch out
test with your own number first, because Run once acts for real.
Voyp2

Delete a Call

ActionIn the docs only

With Delete a Call, a scenario removes a call record from Voyp so your history only keeps what still matters. Pair it with a search so you delete the right item, not the first one that comes back.

When to use it
test calls or duplicates clutter the account after a setup.
Watch out
a delete from a scenario cannot be undone, so check the bundle with Run once first.
Voyp3

Get a Call

ActionIn the docs only

You get the details of one call you already know, ready to map into the next module. Choose it over Search Calls when you know exactly which call you want, rather than a list to sort through.

When to use it
the trigger gives you a call and you need the rest of its information before storing it in a CRM.
Watch out
it works on one call at a time; use Search Calls to find several.
Voyp4

Hangup a Call

ActionIn the docs only

Hangup a Call lets a scenario end a Voyp call, as its name indicates, instead of waiting for someone to put the phone down. The documentation gives no more detail than the name, so read the module's fields in the editor.

When to use it
a call started by Create a Call must be ended by the same automation.
Watch out
test it on a call you placed to yourself.
Voyp5

Make an API Call

ActionIn the docs only

This module opens every endpoint of the Voyp API to your scenario, using the connection you already set up. It covers what the six named modules leave out, without a second login.

When to use it
you need a Voyp feature that none of the other modules offers.
Watch out
the Voyp API is not documented in Make, so you will need Voyp's own API reference to write the request.
Voyp6

Search Calls

SearchIn the docs only

Search Calls brings back the Voyp calls that match your criteria, which may be none, one or many. Each result arrives as its own bundle, so the next module runs once per call found.

When to use it
you want a batch of calls to review before a follow-up, instead of one call at a time.
Watch out
every returned call feeds one operation in the next module, so narrow the search before chaining actions.
Need help

Need help automating Voyp with Make?

A person reads every message.

FAQ

Voyp and Make: common questions

01Is the Voyp Make integration free?
Yes, Voyp is a standard app, so you can use it on Make's Free plan. That plan allows 2 active scenarios, a minimum of 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 (Core, Pro, Teams and Enterprise) drop the minimum interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in operations each month. Your Voyp subscription is a separate matter.
02What do you need to connect Voyp to Make?
You need a Voyp account and a Make account. Make's documentation lists no specific prerequisite for Voyp. You add a Voyp module, click Create a connection, optionally name it, then authorize Make on the Voyp page or paste the key Voyp provides, and click Save. The connection is then shared by every Voyp module in your scenarios, so you only do this once per account. If you manage several Voyp accounts, create one connection per account and give each a clear name.
03Does the Voyp trigger in Make fire instantly?
No. Watch Call Details is a scheduled trigger: Make checks Voyp on the scenario's schedule rather than being called by Voyp through a webhook. A new scenario runs every 15 minutes by default. On the Free plan the shortest gap between two scheduled runs is 15 minutes, and on paid plans it can go down to 1 minute. You change it with the clock on the first module. If a call needs to reach your other tools sooner, a paid plan lets you shorten that gap.
04What if a Voyp module is missing in Make?
Use Make an API Call. It lets your scenario call any endpoint of the Voyp API with the connection you already created, so you can reach features the other six modules do not cover. Keep in mind that Make's documentation for Voyp is limited, because little public information exists about the app, so you will need Voyp's own API reference to know which endpoint to call. Test the request with Run once before you build the rest of the scenario around it.
05Should you use Make or n8n for Voyp?
It depends on your criteria, not on a winner. On Make, Voyp offers 7 modules, a Free plan to start and a visual editor where you test with Run once. The same app often exists as an n8n node too, so check what each tool offers for Voyp, compare the modules you need, and pick the editor your team is comfortable maintaining. The n8n vs Make comparison linked above walks through the differences.
Same platform

Other docs you might need on this stack.

Browse all integrations