Short answer: You can list plivo messages in Plivo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Plivo List Plivo Messages action to a workflow, map its 2 inputs 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 |
|---|---|---|---|
Limit limit | string | Optional | – |
Subaccount Auth ID subaccount | string | Optional | – |
{"limit": "{{trigger.limit}}","subaccount": "{{trigger.subaccount}}"}
{"meta": {"total_count": 1},"objects": [{"to_number": "+1999","from_number": "+1888","message_uuid": "abc","message_state": "delivered"}]}
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.