List Recordings

plivo.list_recordings
ActionVoice & SMSconnection required

Calls the Plivo API with the connection's credentials.

Search stored call recordings by call, number or time, one page at a time.

Connection

Required
Yes — the node will not save without one
Auth type
Username & password
Providers
Plivo
Secret shape
{"username": "<Auth ID>", "password": "<Auth Token>"}
Config it needs
auth_id, src, answer_url, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

8 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
call_uuid
Keep only recordings made during this call.
stringNo———
from_number
Keep only recordings of calls placed from this number.
stringNo———
to_number
Keep only recordings of calls placed to this number.
stringNo———
add_time_gte
Keep only recordings added at or after this time, as YYYY-MM-DD or YYYY-MM-DD HH:MM.
stringNo———
add_time_lte
Keep only recordings added at or before this time.
stringNo———
subaccount
Restrict the search to one subaccount, given as its auth ID.
stringNo———
limit
How many records to return in one page. Plivo caps a page at 20.
numberNo—1–20—
offset
How many records to skip before this page, for paging through a long list.
numberNo—≥ 0—

Output

One shape.

result

FieldTypeExample
items
The records on this page, exactly as Plivo returned them.
array—
count
How many records this page contains.
number—
total_count
How many records match in total, across all pages.
number—
offset
How many records were skipped before this page.
number—
limit
The page size Plivo applied.
number—
next
Relative URI of the next page, or null on the last page.
string—
previous
Relative URI of the previous page, or null on the first.
string—
api_id
Plivo's identifier for this API request.
string—
{
  "api_id": "",
  "count": 0,
  "items": [],
  "limit": 0,
  "next": "",
  "offset": 0,
  "previous": "",
  "total_count": 0
}

See List Recordings run in a workflow.

In a technical demo we add the Plivo connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.