Resources · Make integration

Plivo Make integrationAutomate Plivo with Make.

Every call and text on your Plivo number can start an automation. The Plivo Make integration gives you 9 modules: 5 triggers that notice calls, texts and recordings, and 4 actions that call, speak, answer or text back. This guide walks you through the connection and a first working scenario.

Try the Plivo integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Plivo Make integration do for your phone line?

The Plivo Make integration links your Plivo account to Make, a visual tool where you build a scenario (the automation itself) out of modules (single bricks, each doing one job). Plivo modules react when a call, a text or a recording comes in, and they can place calls or send SMS for you, with no code involved.

Missed-lead follow-up. A property agency lets Call received spot each inbound call, then Send SMS texts the caller a short note with the next step. Nobody on the team has to remember who phoned.

Spoken alerts for urgent jobs. A field service company gets a form entry from another app, and Make call and speak text rings the on-duty technician and reads the job out loud. A phone that rings is harder to ignore than an email.

Recordings that reach the right people. A support desk uses New recording added to pass each fresh recording to the tool where the team reviews calls, instead of digging through the Plivo dashboard.

Keep the scope in mind: Plivo has no search modules in Make and no universal API call module, so anything outside these 9 modules needs a different route. If your team works in n8n, the Plivo n8n integration covers the same app, and n8n vs Make lays out how the two tools differ. If Make itself is new to you, the Make training walks through the editor from scratch, one module at a time.

Connect

How do you connect your Plivo account to Make?

  1. 01

    Grab your Auth ID and Auth Token

    Log in to Plivo and open the dashboard: your Auth ID and Auth Token are shown right there. Copy both somewhere safe, since Make asks for them in a moment. This only works with an active Plivo account.

  2. 02

    Add a Plivo module and open the connection

    In your Make scenario, add any Plivo module and click Create a connection. A connection is your Plivo account linked to Make once, then reused by every Plivo module. The Connection name field is optional, but a clear name helps if you run several accounts.

  3. 03

    Paste the credentials and save

    Enter the Auth ID and Auth Token you copied, or follow the instructions shown on screen, then confirm. Make now lists the connection under that name, and every other Plivo module in your scenarios can pick it from a dropdown.

First scenario

Build your first scenario with Plivo

GoalWhen a text lands on your Plivo number, Make sends the sender an SMS reply straight away.

  1. 01

    Create the scenario

    Go to the Scenarios page in Make, create a new scenario and click the big + in the middle of the editor. That empty circle becomes your first module.

  2. 02

    Pick the instant SMS trigger

    Search for Plivo and choose the instant SMS received module (the one with the lightning badge). Click Create a webhook, then Create a connection and paste your Auth ID and Auth Token.

  3. 03

    Add the reply

    Click the + on the right of the trigger and add Plivo Send SMS. Map the sender's number from the trigger into the recipient, and write a short reply such as a thank-you and your opening hours.

  4. 04

    Test with Run once

    Click Run once, then text your Plivo number from your own phone. Each module shows a bubble with the bundle it received (a bundle is one item passed along, here one message). Check that the reply reached your phone.

  5. 05

    Switch it on

    Once the test looks right, save and turn the scenario on. From then on, every incoming text gets its answer without anyone touching the keyboard. Keep an eye on your first few replies anyway.

Triggers

Plivo triggers: what starts your scenario

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

Plivo1Call received

Call received

Scheduled trigger

In Make“Trigger activates when a new call is received.”

This version of Call received starts a scenario for each new inbound call on your Plivo account, and hands the call details to the next modules as bundles.

How it fires
scheduled, so Make checks the app on the scenario's schedule. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval.
When to use it
keeping a call log where a short wait between the call and the automation changes nothing.
Watch out
an instant twin with the same name exists. Look for the clock badge on this one before you build around it.
Plivo2Call received

Call received

Instant trigger

In Make“Instant trigger activates when a new call is received.”

Here the inbound call itself wakes the scenario up: Plivo tells Make about the new call right after it happens, so any follow-up starts while the caller still remembers you.

How it fires
instant, meaning the app calls Make through a webhook as soon as it happens. The module carries the lightning badge.
When to use it
texting back a caller you could not answer, or alerting a colleague before the moment passes.
Watch out
setup starts with Create a webhook before the connection. Pick this one over its scheduled twin whenever speed matters.
Plivo3New recording added

New recording added

Scheduled trigger

In Make“Trigger activates when there is a new recording.”

A fresh call recording in your Plivo account becomes the starting point of your scenario, ready to be routed to wherever your team listens to calls or keeps records.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a recording shows up in the next check rather than the second it is saved.
When to use it
quality reviews, coaching sessions, or keeping a copy of each recorded call next to the customer file in another app.
Watch out
there is no instant version of this trigger in Make, so plan for the gap between checks.
Plivo4SMS received

SMS received

Scheduled trigger

In Make“Trigger activates when a new SMS is received.”

This scheduled edition of SMS received collects the texts that arrived on your Plivo number since the last check and sends each one down the scenario as its own bundle.

How it fires
scheduled: Make checks the app on the scenario's schedule, which defaults to every 15 minutes.
When to use it
archiving messages into a spreadsheet or a CRM, where nobody waits on the other end for an answer.
Watch out
several texts can arrive between two checks, and each one costs an operation for every module it passes through. An operation is one module run on one bundle, and your plan counts them.
Plivo5SMS received

SMS received

Instant trigger

In Make“Instant trigger activates when a new SMS is received.”

The instant way to catch texts: as soon as a message lands on your Plivo number, Plivo passes it to Make and your scenario runs on that single message.

How it fires
instant. The app calls Make through a webhook as soon as it happens, and the lightning badge on the module confirms it.
When to use it
auto-replies, keyword handling such as a customer texting a booking reference, or pinging a teammate while the sender is still holding the phone.
Watch out
if the same scenario also sends SMS, make sure a reply cannot land back on your own Plivo number, or the scenario could keep triggering itself in a loop.
Modules

Plivo actions: what Make can do on your line

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

Plivo1

Make call and play audio

Action

In Make“Make call and play audio.”

Places an outgoing call through Plivo and plays a prerecorded audio message to whoever picks up, so the person hears a real voice you prepared ahead of time.

When to use it
a recorded announcement that should sound the same every time, like a closing notice or a pickup reminder.
Watch out
Make repeats the action for every bundle it receives, so filter the list before calling people.
Plivo2

Make call and speak text

Action

In Make“Make call and play a message.”

Dials a number and reads a message aloud from text you write in the module, which means the words can change with each run and pull data from earlier modules.

When to use it
a message that varies, such as the name of a client or a job address, where a fixed recording would not fit.
Watch out
run a test call to your own phone first to hear how names and numbers sound.
Plivo3

Respond to incoming call

Action

In Make“Respond to an incoming call with instructions.”

Answers a call coming into Plivo with the instructions you set in Make, so the caller gets a response even when nobody on the team is free to pick up.

When to use it
after hours, or on a line that mostly receives the same question, paired with an incoming call trigger.
Watch out
keep the instructions short and test them by calling the number yourself before you switch the scenario on.
Plivo4

Send SMS

Action

In Make“Send sms to a plivo number when there is a trigger.”

Sends a text message through your Plivo account when something happens earlier in the scenario, in Plivo or in any other app connected to Make.

When to use it
confirmations, reminders or alerts, for instance texting a customer once an order changes status in your shop tool.
Watch out
map the recipient from the previous module rather than typing it, or every text will reach the same number.
Need help

Need help automating Plivo with Make?

A person reads every message.

FAQ

Plivo and Make: common questions

01Is the Plivo Make integration free to use?
Yes. Plivo is a standard app in Make, so its 9 modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Keep in mind that Plivo bills its own service separately; check the Plivo pricing page for that side, since Make does not cover it.
02What does it take to connect Plivo to Make?
You need an active Plivo account and two values from its dashboard: the Auth ID and the Auth Token. In Make, add any Plivo module, click Create a connection, give it a name if you like, and paste both values. Picked an instant module? Click Create a webhook first; the connection follows. Once saved, the same connection serves every Plivo module in all your scenarios, so you only do this once per account.
03Do Plivo triggers in Make react in real time?
Yes, for calls and texts. Call received and SMS received each exist in an instant version, where Plivo alerts Make through a webhook as soon as the event happens. They also exist in a scheduled version, which Make checks on the scenario's schedule, every 15 minutes by default. New recording added is only available as a scheduled trigger, so a new recording arrives in Make at the next check. Look at the badge on the module: lightning means instant, a clock means scheduled.
04What are the options when a Plivo module is missing in Make?
It depends on what you need. The Plivo app in Make has 9 modules and no universal API call module, so you cannot fill the gap from inside the app. You can often build around it with modules from other apps: another tool can store data, look up a contact or format a message before a Plivo action runs. If the job truly needs something Plivo does not offer in Make, the Hack'celeration team can look at your case and suggest a workable route.
05Make or n8n: which one fits Plivo automations?
It depends on where your automations already live. Plivo is available in both tools. In Make you get 5 triggers, including instant versions for calls and texts, plus 4 actions for calling and texting, all set up visually with a guided connection. The same app has an n8n node too, so if your team already builds in n8n, staying there avoids running two tools side by side. Compare the list of modules against your use case, then pick the tool your team is comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations