ActionPlivoUpdated May 2026

How do I fetch a Plivo message's status?

Short answer: Drop the "Plivo → Get Plivo Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Plivo actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Message UUID message_uuid	string	Required	The Message UUID assigned by Plivo. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.

Sample request

{
  "message_uuid": "{{trigger.message_uuid}}"
}

Returns

{
  "to_number": "+1999",
  "from_number": "+1888",
  "message_uuid": "abc",
  "message_state": "delivered",
  "message_direction": "outbound"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Plivo Message.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Plivo

2 Google Sheets triggers

HubSpot → Plivo

18 HubSpot triggers

FAQ

Questions about Get Plivo Message.

What does the Get Plivo Message action do in Plivo?

Returns the message by UUID with status, delivery info. For polling-based delivery confirmation when webhooks aren't configured.

What inputs does Get Plivo Message require?

Required: Message UUID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Plivo returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Plivo Message support batch operations?

Yes. Run Get Plivo Message inside a Loop node to process arrays. Tiny Command handles Plivo's rate limits automatically so you don't have to throttle manually.

More actions