Short answer: You can get plivo message in Plivo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Plivo Get Plivo Message action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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. |
{"message_uuid": "{{trigger.message_uuid}}"}
{"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.
Any of these apps can fire this action as part of a workflow.