--- title: "Plivo Integration" description: "Send SMS and MMS, place outbound voice calls, and manage rented phone numbers and applications through the Plivo cloud communications platform." url: https://flowrunner.ai/integrations/plivo date_modified: 2026-08-01T02:40:32-07:00 --- # Plivo [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Send SMS and MMS, place outbound voice calls, and manage rented phone numbers and applications through the Plivo cloud communications platform. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 14 actions · Basic auth · available [Plivo website](https://plivo.com/) · [Platform Documentation](https://www.plivo.com/docs/) · Capability data verified 2026-07-14 1. An incident or event needs to reach a person by voice 2. Agent pulls the recipient number and the answer URL for the call 3. Agent confirms account standing with Get Account Details 4. Agent confirms the call script and recipient before dialing 5. Agent places the call with Make Call 6. Agent records the call outcome with Get Call 7. A voice blast to a pulled contact list waits for approval before it dials ## What This Integration Enables An agent can send transactional or notification SMS and MMS to one or many recipients, joining destination numbers with the delimiter Plivo expects for multi-recipient sends. It can place outbound voice calls driven by answer URLs, look up delivery status and call detail records, and search, buy, and manage rented numbers, applications, and Powerpack sender pools. It can also monitor account balance and credits so a workflow knows when funds are running low. ### Without FlowRunner **Text-only escalation**: Urgent alerts sit unread in a phone that is on silent **No call records in flow**: Delivery and call outcomes are checked by hand in the console **Numbers managed manually**: Rented numbers and applications are configured outside the workflow ### With FlowRunner **Voice reaches directly**: The agent places a call when a text is not enough **Outcomes tracked in flow**: Get Message and Get Call pull delivery status and call records automatically **Numbers managed in flow**: Search, buy, and inspect numbers as part of the workflow ## Use Case Scenarios ### Voice escalation for a missed incident An incident escalates and a text alert has gone unacknowledged. The agent places an outbound call with Make Call, pointing Plivo at an answer URL that reads the incident details to the on-call engineer. It tracks the outcome with Get Call to confirm the call connected. Voice reaches someone whose phone is on silent when a text would not. ### Multi-recipient SMS broadcast A workflow needs to notify a list of contacts at once. The agent pulls the numbers, joins them with the delimiter Plivo uses for multi-recipient sends, and delivers the notification with Send SMS, which returns one message identifier per recipient. It then reviews delivery with List Messages to catch any that failed. ### Voice campaign with a dial gate A team wants to run an automated voice reminder to a pulled contact list. The agent assembles the list and prepares the answer URL, then reaches the human-in-the-loop step because a voice campaign reaches people directly on their phones. A person approves the list and the script before the agent begins dialing. ## Human-in-Loop Highlight A voice call interrupts a person the moment it rings, and a campaign multiplies that across an entire list. Before the agent runs an outbound voice blast to a pulled contact list, it pauses and routes the decision to an operator: "Ready to place automated calls to 210 contacts using the reminder answer URL. Approve the list and script, or hold?" This is FlowRunner's human-in-the-loop pattern: the agent stops on its own, presents the audience and the call script, and resumes when the human answers. A single escalation call to one on-call engineer dials without interruption. A campaign that rings a whole list gets a human decision first. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 14 actions ### Messaging 3 - **Send SMS** Sends an SMS or MMS to one or more recipients, joining destinations with the delimiter Plivo expects for multi-recipient sends and returning one message identifier per recipient. Used for transactional and broadcast text and multimedia. - **Get Message** Retrieves a single message by its UUID, including delivery status, sender, recipient, and body. Used to confirm whether a message was delivered. - **List Messages** Pages through messages sent and received by the account, with optional time filtering. Used to review recent message activity. ### Voice 4 - **Make Call** Initiates an outbound call from a Plivo number, fetching XML call instructions from the provided answer URL when the call is answered. Used for automated voice alerts and reminders. - **Get Call** Retrieves details for a single call by its UUID, including status, direction, duration, and cost, for live or completed calls. Used to confirm a call's outcome. - **List Calls** Pages through completed calls (Call Detail Records) with optional direction filtering. Used to review call activity. - **Hangup Call** Terminates a live call immediately by its UUID. Used to end a call the workflow no longer needs. ### Numbers 4 - **Search Numbers** Searches Plivo inventory for available numbers to rent, filtered by country and type. Used to find a number before buying it. - **Buy Number** Rents an available number found via search and adds it to the account, optionally associating it with an application. Used to provision a new sender number. - **List Numbers** Pages through numbers currently rented on the account, with optional type filtering. Used to audit owned numbers. - **Get Number** Retrieves the details of a single rented number, including capabilities and application association. Used to inspect one number. ### Powerpacks 1 - **List Powerpacks** Pages through Powerpacks, which group sender numbers and IDs into a pool Plivo selects from automatically when sending. Used to review configured sender pools. ### Applications 1 - **List Applications** Pages through Plivo applications, which hold reusable voice and messaging configuration that can be attached to numbers. Used to review application setup. ### Account 1 - **Get Account Details** Retrieves the account name, current balance, available credits, and account type. Used to confirm standing and funds before sending. ## Frequently Asked Questions ### What can FlowRunner do with Plivo? FlowRunner agents can run Send SMS, Get Message, and List Messages in Plivo, plus 11 more actions. ### Does connecting Plivo to FlowRunner require OAuth? No. Plivo connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Plivo trigger a FlowRunner workflow automatically? Plivo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Plivo?** This integration exposes Plivo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/plivo. Site index: https://flowrunner.ai/llms.txt