Appearance
Plivo
undefined
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://api.plivo.com/v1/Account/{auth_id} |
| Authentication | Basic Auth |
| Endpoints | 6 |
| Connector key | plivo |
Using Plivo in a workflow
- Go to Connections and click New Connection.
- Pick Plivo from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
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
| Detail | Value |
|---|---|
| Operation ID | send_message_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Plivo connection from the Connection dropdown.
- In the Operation dropdown, select
send_message_0. - 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
| Detail | Value |
|---|---|
| Operation ID | make_call_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Plivo connection from the Connection dropdown.
- In the Operation dropdown, select
make_call_1. - 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
| Detail | Value |
|---|---|
| Operation ID | list_numbers_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Plivo connection from the Connection dropdown.
- In the Operation dropdown, select
list_numbers_2. - 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
| Detail | Value |
|---|---|
| Operation ID | search_numbers_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Plivo connection from the Connection dropdown.
- In the Operation dropdown, select
search_numbers_3. - 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
| Detail | Value |
|---|---|
| Operation ID | list_recordings_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Plivo connection from the Connection dropdown.
- In the Operation dropdown, select
list_recordings_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
| Detail | Value |
|---|---|
| Operation ID | list_applications_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Plivo connection from the Connection dropdown.
- In the Operation dropdown, select
list_applications_5. - 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.