Appearance
Vonage
undefined
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://api.nexmo.com |
| Authentication | Bearer Token |
| Endpoints | 7 |
| Connector key | vonage |
Using Vonage in a workflow
- Go to Connections and click New Connection.
- Pick Vonage 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 SMS |
GET | Send Message |
GET | Start Verification |
GET | Create Call |
GET | List Calls |
GET | Search Numbers |
GET | Get Balance |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Send SMS
| Detail | Value |
|---|---|
| Operation ID | send_sms_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vonage connection from the Connection dropdown.
- In the Operation dropdown, select
send_sms_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 Vonage API reference.
GET
Send Message
| Detail | Value |
|---|---|
| Operation ID | send_message_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vonage connection from the Connection dropdown.
- In the Operation dropdown, select
send_message_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 Vonage API reference.
GET
Start Verification
| Detail | Value |
|---|---|
| Operation ID | start_verification_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vonage connection from the Connection dropdown.
- In the Operation dropdown, select
start_verification_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 Vonage API reference.
GET
Create Call
| Detail | Value |
|---|---|
| Operation ID | create_call_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vonage connection from the Connection dropdown.
- In the Operation dropdown, select
create_call_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 Vonage API reference.
GET
List Calls
| Detail | Value |
|---|---|
| Operation ID | list_calls_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vonage connection from the Connection dropdown.
- In the Operation dropdown, select
list_calls_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 Vonage API reference.
GET
Search Numbers
| Detail | Value |
|---|---|
| Operation ID | search_numbers_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vonage connection from the Connection dropdown.
- In the Operation dropdown, select
search_numbers_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 Vonage API reference.
GET
Get Balance
| Detail | Value |
|---|---|
| Operation ID | get_balance_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vonage connection from the Connection dropdown.
- In the Operation dropdown, select
get_balance_6. - 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 Vonage API reference.