Resources · Make integration

Voxloud Make integrationAutomate Voxloud with Make.

What if every phone call could start a task on its own? The Voxloud Make integration gives you 5 modules: 4 instant triggers that follow a call from ring to hang up, plus one open API module. This page shows how to link your account and build a first scenario.

Try the Voxloud integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Voxloud Make integration do?

The Voxloud Make integration links your Voxloud phone system to Make, a no-code tool where you build a scenario: an automation made of modules, one brick per step. Voxloud tells Make the moment something happens on a call, and your scenario takes it from there without anyone copying details by hand.

Follow up after every conversation. Watch Call Hang Up fires when a call ends, which is the natural moment to log the exchange in another tool your team uses or to open a follow-up task for the salesperson who took it.

Warn the team before anyone picks up. Watch Call Incoming reacts while the phone is still ringing. A support desk can use it to post an alert in a shared channel, so the right person knows a call is on its way.

Track what really gets answered. Watch Call Answered and Watch New Phone Call let you separate calls that went through Voxloud from calls someone actually took, a simple way to spot missed demand.

The catalog stops at those four triggers and one action, Make an API Call, which reaches any endpoint of the Voxloud API with the same account link. Voxloud's own Make documentation also warns that it is AI-generated from the vendor's docs, so check important details with Voxloud. Before picking a tool, the n8n vs Make comparison lays out the criteria, and the Make training walks you through the editor step by step.

Connect

How do you connect Voxloud to Make?

  1. 01

    Generate an API key in Voxloud

    Open your Voxloud dashboard, go to the API Keys section and click Generate. Copy the key right away, since Voxloud shows it while you create it. You need an active Voxloud account for this.

  2. 02

    Add a Voxloud module in Make

    In your scenario, add any Voxloud module and click Create a connection. A connection is your Voxloud account linked to Make once, then reused by every Voxloud module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions shown on screen, then save. From now on Make can talk to your Voxloud account whenever the scenario runs.

First scenario

Build your first scenario with Voxloud

GoalWhen a call ends in Voxloud, Make sends a request to the Voxloud API that you choose from its documentation.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. That first module decides when everything starts.

  2. 02

    Pick Watch Call Hang Up

    Search for Voxloud, choose Watch Call Hang Up, click Create a webhook, then Create a connection with your API key. Voxloud will now warn Make at the end of each call.

  3. 03

    Add Make an API Call

    Click the + on the right of the trigger, pick Voxloud again and choose Make an API Call. It reuses the same connection. Map data from the trigger into the request you need.

  4. 04

    Test with Run once

    Click Run once, then place or end a short test call. Each module shows the bundles it received, a bundle being one item passed from module to module, here one call.

  5. 05

    Switch the scenario on

    Once the test looks right, turn the scenario on. With an instant trigger there is no clock to tune: Make runs the scenario each time Voxloud reports a finished call.

Triggers

Which Voxloud events can start a scenario?

4 modules start a scenario when something happens in Voxloud. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Voxloud as soon as it happens.

Voxloud1Watch Call Answered

Watch Call Answered

Instant trigger

In Make“Triggers when a call is answered.”

You get a scenario that starts the moment someone picks up a call in Voxloud, so any follow-up can begin while the conversation is still going on.

How it fires
instant, Voxloud calls Make through a webhook as soon as the call is answered, with no schedule to set.
When to use it
choose it over Watch Call Incoming when only the conversations that actually happened matter, for example to count answered calls per team or to open a record once a client is on the line.
Watch out
an unanswered call never reaches this trigger, so pair it with another trigger if missed calls matter to you.
Voxloud2Watch Call Hang Up

Watch Call Hang Up

Instant trigger

In Make“Triggers when a call was hung up.”

This one hands you the end of the call, the point where a conversation turns into work to do: a note, a task, a message to a colleague.

How it fires
instant, Voxloud notifies Make through a webhook as soon as the line is hung up.
When to use it
pick it for anything that should happen after the talk is over, such as logging the exchange in a customer tool or asking a salesperson to write a recap.
Watch out
every finished call becomes one run, and each module in that run counts as an operation on your Make plan, so add a filter if only some calls deserve a follow-up.
Voxloud3Watch Call Incoming

Watch Call Incoming

Instant trigger

In Make“Triggers when a phone call is incoming.”

Your scenario learns about a call while the phone is still ringing, which gives your team a head start before anyone answers.

How it fires
instant, Voxloud pushes the event to Make through a webhook as soon as the incoming call starts.
When to use it
a support desk that wants a heads up in its shared channel, or a front office that wants to prepare the caller's file before picking up.
Watch out
the scenario fires whether or not the call is answered later, so keep this for alerts and use Watch Call Answered when you only want real conversations.
Voxloud4Watch New Phone Call

Watch New Phone Call

Instant trigger

In Make“Triggers when a new call is going through Voxloud.”

Here you catch every new call passing through Voxloud, which makes it the widest net of the four triggers and a good base for a full call log.

How it fires
instant, Voxloud tells Make through a webhook the moment a new call goes through the system.
When to use it
when you want one scenario that sees all traffic, for instance to feed a spreadsheet that the manager reads to understand call volume by line.
Watch out
as it sees every call, it will likely catch calls that the three narrower triggers also report; running several on the same calls multiplies your operations.
Modules

What else can Make do in Voxloud?

Voxloud gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Voxloud1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach any endpoint of the Voxloud API from your scenario, using the connection you already created, so you are not limited to the four listed triggers.

When to use it
as soon as you need something from Voxloud that no ready-made module offers, after reading the Voxloud API documentation to find the right endpoint.
Watch out
you build the request yourself, so a wrong path fails; test it with Run once before switching on. For recurring errors, the Make troubleshooting guide helps.
Need help

Need help automating Voxloud with Make?

A person reads every message.

FAQ

Voxloud and Make: common questions

01Is the Voxloud Make integration free?
Yes, on the Make side. Voxloud is a standard app, so it works from the Free plan, which allows 2 active scenarios, a run time of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Since all four Voxloud triggers are instant, the 15 minute minimum interval of the Free plan does not slow them down. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and count usage in credits each month. You still need your own Voxloud subscription, which Voxloud prices separately.
02What do you need to connect Voxloud to Make?
You need an active Voxloud account and an API key. Generate the key from the API Keys section of your Voxloud dashboard with the Generate button, and copy it while it is displayed. In Make, add a Voxloud module, click Create a connection, give it a name if you like and paste the key. For any of the four instant triggers, click Create a webhook before creating the connection. Once saved, the same connection serves every Voxloud module in all your scenarios, so you only do this once per account.
03Do Voxloud triggers in Make fire in real time?
Yes. All four Voxloud triggers, Watch Call Answered, Watch Call Hang Up, Watch Call Incoming and Watch New Phone Call, are instant. Voxloud calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. That is why the module shows a lightning badge rather than a clock. In practice, your scenario starts as the call rings, is answered or ends, and the 15 minute default schedule of new scenarios does not apply to them.
04What if the Voxloud module you need is missing in Make?
Use Make an API Call. It sends any request to the Voxloud API with the connection you already set up, so it covers whatever the four triggers do not. You pick the endpoint from the Voxloud API documentation, build the request, then test it with Run once. Keep in mind that the Make documentation for Voxloud is flagged as AI-generated from the vendor's docs and may contain mistakes, so confirm anything important with Voxloud directly before relying on it in a live scenario.
05Should you use Make or n8n for Voxloud?
It depends on your criteria rather than on Voxloud itself. In Make, Voxloud comes with 4 instant triggers and Make an API Call, it is available from the Free plan, and every module uses one connection built on your API key. The same app often has an n8n node too, so check what that node covers before you decide. Look at which triggers you need, which tool your team already runs and how you want to be billed; the comparison page linked above goes through those points.
Same platform

Other docs you might need on this stack.

Browse all integrations