Resources · Make integration

Nvoip Make integrationAutomate Nvoip with Make.

Can Make place calls and send texts through Nvoip for you? The Nvoip Make integration gives you 7 action modules for calls, voice broadcasts, SMS and WhatsApp templates. This guide shows how to link your account and build a first scenario that sends a message when something happens elsewhere.

Try the Nvoip integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Nvoip Make integration do for you?

The Nvoip Make integration lets a Make scenario (the automation you build, a chain of steps) reach people through your Nvoip account: a phone call, a voice broadcast, an SMS or a WhatsApp template. Nvoip only acts here; the event that starts the flow comes from another app or from a schedule.

Confirm an order by text. A store app reports a new order, and Send a SMS Message writes to the buyer with the order details mapped from the previous step. The customer hears from you without anyone typing a message.

Warn a whole list at once. When a service outage is logged in your ticketing tool, Make a Voice Broadcast or Make a Interactive Voice Broadcast reaches the affected contacts by phone, which suits people who rarely read texts.

Keep messaging consistent. Support teams that answer on WhatsApp can use Send a WhatsApp Template, and marketers who reuse the same SMS wording can rely on Send a SMS Template.

Know the boundaries before you start. Nvoip has no trigger module in Make, so it cannot start a scenario when a call ends or a text comes back. The Make documentation for Nvoip is also flagged as AI-generated from the vendor's own docs, so confirm details with Nvoip when something matters. If you are still weighing platforms, read our Make review and the n8n vs Make comparison; if a scenario misbehaves, Make troubleshooting covers the common errors.

Connect

How do you connect Nvoip to Make?

  1. 01

    Copy your Nvoip token

    Log in to Nvoip and open the API section or your account settings. Look for the area labeled Token or API Token and copy the authentication token shown there. You need an active Nvoip account for this.

  2. 02

    Open the connection window

    In your Make scenario, add any Nvoip module and click Create a connection. A connection is your Nvoip account linked to Make once; every Nvoip module in your scenarios reuses it afterwards.

  3. 03

    Paste the token and save

    Give the connection a recognizable label in Connection name if you like, then enter the credentials you copied from Nvoip or follow the on-screen instructions. Save, and Make is ready to use your account.

First scenario

Build your first scenario with Nvoip

GoalWhen a new entry arrives in another app, Make texts the person through Nvoip and then places a call.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + to add the first module. Since Nvoip has no trigger, this first bubble belongs to the app where your contacts come from.

  2. 02

    Set the starting app

    Pick the trigger of that other app, such as a new form entry or a new CRM record, and connect its account. Each new entry becomes a bundle: one item passed to the next module.

  3. 03

    Add Send a SMS Message

    Click the + on the right, search for Nvoip, choose Send a SMS Message and select your connection. Map the phone number and the text from the data of the first module.

  4. 04

    Chain Make a Call

    Add Make a Call after the SMS step with the same connection, mapping the same phone number, so the contact gets a text first and then a call.

  5. 05

    Test with Run once

    Click Run once and create a test entry with your own number. Read the bundles each module received; the text and the call are real, so keep tests on your own phone.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What each Nvoip module does

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

Nvoip1

Make a Voice Broadcast

ActionIn the docs only

Sends one spoken message to many people through Nvoip, so an announcement reaches phones instead of inboxes that nobody opens.

When to use it
a school or clinic that must tell every contact about a closure as soon as it is logged in another tool.
Watch out
the Make documentation gives no detail on the fields, so check in Nvoip how a broadcast audience and audio are set before you rely on it.
Nvoip2

Make a Call

ActionIn the docs only

Places a single phone call from your Nvoip account to one number, which turns an event in another app into a ring on the right phone.

When to use it
a high-value lead fills out a form and you want the contact reached by phone right after, not whenever someone gets round to calling back.
Watch out
the module acts once per bundle it receives, so a step that outputs ten contacts produces ten calls.
Nvoip3

Make a Interactive Voice Broadcast

ActionIn the docs only

Runs a voice broadcast in which people can respond, as the module name indicates, which gives you more than a one-way announcement.

When to use it
appointment reminders where the patient or client should be able to answer instead of just listening.
Watch out
the documentation does not describe how answers come back, and Nvoip has no trigger in Make, so plan how you will read the responses in Nvoip itself.
Nvoip4

Make an API Call

ActionIn the docs only

Calls any endpoint of the Nvoip API from your scenario, reusing the same connection, so a feature missing from the six ready-made modules is still within reach.

When to use it
when you need something from Nvoip that no listed module offers, and the Nvoip API documentation shows the endpoint for it.
Watch out
you build the request yourself, so keep the vendor's API reference open while you set the path and body.
Nvoip5

Send a SMS Message

ActionIn the docs only

Sends a text to a phone number with wording you compose right in the scenario, mixing fixed words and data mapped from earlier modules.

When to use it
an order confirmation or a delivery notice where each message carries the customer's name and order details.
Watch out
every Run once really sends the text, so test with your own number before you map real customer data.
Nvoip6

Send a SMS Template

ActionIn the docs only

Sends an SMS built on a template, as the module name says, so your team reuses approved wording instead of rewriting it in each scenario.

When to use it
recurring messages such as payment reminders, where legal or marketing has already validated the text.
Watch out
the Make documentation says nothing about where templates live, so confirm in your Nvoip account how they are created before building on this module.
Nvoip7

Send a WhatsApp Template

ActionIn the docs only

Delivers a WhatsApp message based on a template through Nvoip, so the update reaches customers on WhatsApp instead of by email.

When to use it
a support ticket changes status and the customer should get the update on WhatsApp rather than by email.
Watch out
the documentation for this module is thin and marked as AI-generated, so check with Nvoip which templates your account can send.
Need help

Need help automating Nvoip with Make?

A person reads every message.

FAQ

Nvoip and Make: common questions

01Is the Nvoip Make integration free?
Yes, on the Make side. Nvoip is a standard app, so its modules work on the Free plan as well as on paid plans. The Free plan has limits: 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 (Core, Pro, Teams and Enterprise) bring a 1 minute minimum interval, unlimited active scenarios and 40 minutes of execution, and count usage in credits, meaning operations, per month. Your Nvoip account and its own costs are a separate matter to check with Nvoip.
02What do you need to connect Nvoip to Make?
An active Nvoip account and its authentication token. Log in to Nvoip, open the API section or the account settings, find the part labeled Token or API Token and copy the token. Then, in Make, add any Nvoip module, click Create a connection, optionally name it and paste the token. That connection is saved once and reused by all seven Nvoip modules, so you do not repeat the step for each module or each new scenario. If the token is rejected, copy it again in full from Nvoip.
03Does the Nvoip Make integration react in real time?
No, because Nvoip has no trigger module in Make: it cannot start a scenario on its own. The scenario begins with another app instead. If that app has an instant trigger, it calls Make through a webhook as soon as something happens, and the Nvoip step follows right after. If it has a scheduled trigger, Make checks it on the scenario's schedule, every 15 minutes by default. You can also start from a plain schedule in Make, then let a Nvoip module send the message when the run finds something to act on.
04What if a Nvoip module you need is missing in Make?
Use Make an API Call. Nvoip has this module, which calls any endpoint of the Nvoip API from your scenario with the same connection as the other modules. It covers what the six ready-made modules leave out, as long as the Nvoip API offers it. Keep in mind that the Make documentation for Nvoip is marked as AI-generated from the vendor's docs and may contain errors, so verify the endpoint and its details with Nvoip before relying on it in production.
05Should you use Make or n8n for Nvoip?
It depends on the tool your team already works in and on the modules you need. On Make, Nvoip offers seven action modules for calls, voice broadcasts, SMS and WhatsApp templates, plus Make an API Call for the rest, and no trigger. Many apps also have an n8n node, so check whether one exists for Nvoip and what it covers before choosing. Compare the two on the actions you actually plan to run rather than on reputation. Our n8n vs Make comparison, linked earlier on this page, lays out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations