Resources · n8n integration

Plivo n8n integrationAutomate Plivo with n8n.

Can a workflow pick up the phone? With the Plivo n8n integration it can. The node ships with n8n and exposes 3 operations across 3 resources: SMS, MMS and Call. One credential, the login n8n stores once, and any workflow reaches a phone instead of an inbox.

Try the Plivo integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Plivo n8n integration actually do?

The Plivo node turns a phone number into something a workflow can write to. It ships with n8n, so there is nothing to install: pick a resource (SMS, MMS or Call), fill in From and To, and the step runs like any other node on the canvas.

Three resources, one operation each, no trigger node. Plivo sits at the outbound end of a workflow, the part that reaches a person who is not watching a screen.

Start with the plainest one. A workflow reads a fresh row from Google Sheets, and the row holds a customer phone number and an order reference. The SMS operation takes the number into To, a short confirmation into Message, and that is the whole step. No template engine, no formatting layer, just the text you assembled in the node before.

The second one is louder. A nightly job fails, and an email sitting in a queue at 3am helps nobody. The Call operation dials the on-call number and hands the conversation to an Answer URL that returns the XML Plivo uses to run the call. The same workflow can still post the details to Slack so the written trace exists somewhere, while the phone does the waking up.

The third one carries files. MMS takes a comma-separated list in Media URLs, pointing at files already sitting on your own file server, so a delivery photo or a generated visual travels with the message. Teams that already push text alerts to Telegram use MMS for the cases where the recipient has no app installed and a phone number is the only address you have.

When the thing you need is not one of those three, HTTP Request is the way out. That node calls any endpoint of the Plivo API and reuses the very same credential through predefined authentication, so you keep one set of keys and change only the URL. It is the standard move for this whole family of nodes, and it costs a few extra fields rather than a rewrite.

Worth knowing before you build: there is no Plivo trigger, so every workflow here starts with a Schedule Trigger, an n8n Webhook, or another tool's trigger. n8n's own template library has a worked example, a daily weather update sent to a phone number, workflow 1005, which is a compact way to see the node wired up end to end. If you are weighing n8n against other platforms first, the n8n review goes through it, and the n8n training covers the build habits this page assumes.

Connect

How do you connect Plivo to n8n?

  1. 01

    Grab your Auth ID and Auth Token

    Create a Plivo account, then open the Overview page of the Plivo console. Two values live there. The Auth ID acts like a username and the Auth Token acts like a password. Copy both. Plivo publishes a support article on changing either value later, so a rotation is not a dead end.

  2. 02

    Store them once as an n8n credential

    Open the Credentials menu in n8n and create a Plivo credential, the record n8n keeps so a node can authenticate without you pasting keys into it. Plivo supports Basic auth and nothing else here, so the form asks for those two values and stops. Every workflow on the instance then picks that credential from a dropdown.

  3. 03

    Add the node and choose a resource

    Drop the Plivo node on the canvas and choose between the SMS, MMS and Call resources. Each one carries a single operation, so the second dropdown settles itself. Put a Plivo number in From, written like the placeholder +14156667777, put the destination in To, and run the step once before you wire anything behind it.

Actions

What the Plivo node can do

The Plivo node exposes 3 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceMakeSend
Call✓
MMS✓
SMS✓

Call

1 operation
01

Make a call

call.make

What you see in n8n

Notes & use cases

Plivo dials the number you pass and, the moment the call is answered, fetches the instructions that drive it. The call logic lives in that returned XML, not inside n8n.

Key parameters

  • From: the caller ID for the call to make, written like the placeholder +14156667777.
  • To: the number Plivo dials, often {{ $json.field }} taken from the step before.
  • Answer URL: the URL Plivo invokes once the call is answered. It should return the XML that handles the call.
  • Answer Method: GET or POST, the HTTP verb used when invoking that Answer URL.
Use cases
an escalation path where a failed nightly job rings whoever is on call, rather than adding one more unread line to a mailbox.

MMS

1 operation
02

Send an MMS

mms.send

What you see in n8n

Notes & use cases

Same shape as a text message, with files riding along, except Plivo only delivers MMS to US and Canada numbers. n8n hands Plivo the numbers plus whatever you attached, and the workflow carries on.

Key parameters

  • From: the Plivo number the MMS is sent from, required, in the form +14156667777.
  • To: the destination number, required, commonly {{ $json.field }} from an earlier node.
  • Media URLs: a comma-separated list of media URLs of the files from your file server.
  • Message: the text that travels with the media.
Use cases
a field team closing a job sends the signed delivery photo to the customer's number straight from the workflow that logged the job.

SMS

1 operation
03

Send an SMS

sms.send

What you see in n8n

Notes & use cases

One step, one text message. Three required boxes, nothing optional to weigh up, which makes this the operation most workflows reach for first.

Key parameters

  • From: the Plivo number the SMS is sent from, required.
  • To: the number the message goes to, required, usually {{ $json.field }} mapped from the incoming item.
  • Message: the body of the text, required. A required field left empty stops the node from executing, so build the string in an earlier step if it depends on data.
Use cases
an appointment reminder fired a day ahead by a Schedule Trigger reading the day's bookings.
Need help

Need help automating Plivo with n8n?

A person reads every message.

FAQ

Plivo and n8n, questions people ask

01Is the Plivo n8n integration free?
On the n8n side, yes. Nothing to install. The node ships with n8n, so there is no plugin to buy and no extra n8n charge for dropping it into a workflow. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license. What Plivo bills on its own side is a separate question and this page does not cover it, so check your Plivo account for that. The only spend inside n8n is the few minutes it takes to create one credential. That credential then serves every workflow on the instance, however many phone numbers you end up texting.
02What credentials do you need for the Plivo node?
One Basic auth credential, and that is the only supported method. It takes two values: an Auth ID, which acts like a username, and an Auth Token, which acts like a password. Both sit on the Overview page of the Plivo console once the account exists. In n8n you create the credential once from the Credentials menu, and each Plivo node afterwards selects it from a dropdown rather than holding keys of its own. If either value is rotated later, Plivo documents how, and you update that single credential record instead of touching every workflow.
03What are the limits of the Plivo node in n8n?
The node covers 3 operations across 3 resources: making a voice call, sending an SMS, sending an MMS. That is the catalog. For anything in the Plivo API outside those, the HTTP Request node calls any endpoint of the service and reuses the same Plivo credential through predefined authentication, so one set of keys serves both paths and only the URL changes. The other thing to plan around is the required fields: a field marked required stops the node from executing when it is empty, so make sure From, To and the rest are populated by the time the workflow runs on its own.
04Is there a Plivo trigger in n8n?
No, Plivo has no trigger node, so a workflow using it always starts somewhere else. Two patterns cover most of it. The Schedule Trigger runs the workflow on a fixed interval, which suits a daily digest or a reminder sent the morning before an appointment. The n8n Webhook node gives you a URL that a third-party service calls, which suits a form submission or an alert coming out of a monitoring tool. You can also hang the Plivo node off another tool's trigger, so a new row, a new ticket or a new signup turns into a message. Plivo is the last step here, never the first.
05n8n or Make for Plivo?
It comes down to what you want to own. Make is a hosted automation platform with no self-hosting option, billed per operation, which is simple to start and ties your cost to volume. n8n runs on n8n Cloud or on your own server, which matters when phone numbers and message bodies should stay inside your own infrastructure. Both give you a visual canvas and both reach Plivo. Choose Make if you want zero infrastructure to look after. Choose n8n if you want control over where the data sits, a cost model shaped by your hosting choice, and the option to drop into HTTP Request for anything outside the 3 operations.
Same platform

Other docs you might need on this stack.

Browse all integrations