Skip to content
For LLMsView as Markdown·

Plivo

undefined

DetailValue
CategoryCommunication
Base URLhttps://api.plivo.com/v1/Account/{auth_id}
AuthenticationBasic Auth
Endpoints6
Connector keyplivo

Using Plivo in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Plivo from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET Send Message
GET Make Call
GET List Numbers
GET Search Numbers
GET List Recordings
GET List Applications

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Send Message

DetailValue
Operation IDsend_message_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Plivo connection from the Connection dropdown.
  3. In the Operation dropdown, select send_message_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Plivo API reference.

GET

Make Call

DetailValue
Operation IDmake_call_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Plivo connection from the Connection dropdown.
  3. In the Operation dropdown, select make_call_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Plivo API reference.

GET

List Numbers

DetailValue
Operation IDlist_numbers_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Plivo connection from the Connection dropdown.
  3. In the Operation dropdown, select list_numbers_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Plivo API reference.

GET

Search Numbers

DetailValue
Operation IDsearch_numbers_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Plivo connection from the Connection dropdown.
  3. In the Operation dropdown, select search_numbers_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Plivo API reference.

GET

List Recordings

DetailValue
Operation IDlist_recordings_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Plivo connection from the Connection dropdown.
  3. In the Operation dropdown, select list_recordings_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Plivo API reference.

GET

List Applications

DetailValue
Operation IDlist_applications_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Plivo connection from the Connection dropdown.
  3. In the Operation dropdown, select list_applications_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Plivo API reference.