Skip to content
For LLMsView as Markdown·

Vonage

undefined

DetailValue
CategoryCommunication
Base URLhttps://api.nexmo.com
AuthenticationBearer Token
Endpoints7
Connector keyvonage

Using Vonage in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Vonage 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 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

DetailValue
Operation IDsend_sms_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Vonage connection from the Connection dropdown.
  3. In the Operation dropdown, select send_sms_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 Vonage API reference.

GET

Send Message

DetailValue
Operation IDsend_message_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Vonage connection from the Connection dropdown.
  3. In the Operation dropdown, select send_message_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 Vonage API reference.

GET

Start Verification

DetailValue
Operation IDstart_verification_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Vonage connection from the Connection dropdown.
  3. In the Operation dropdown, select start_verification_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 Vonage API reference.

GET

Create Call

DetailValue
Operation IDcreate_call_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Vonage connection from the Connection dropdown.
  3. In the Operation dropdown, select create_call_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 Vonage API reference.

GET

List Calls

DetailValue
Operation IDlist_calls_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Vonage connection from the Connection dropdown.
  3. In the Operation dropdown, select list_calls_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 Vonage API reference.

GET

Search Numbers

DetailValue
Operation IDsearch_numbers_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Vonage connection from the Connection dropdown.
  3. In the Operation dropdown, select search_numbers_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 Vonage API reference.

GET

Get Balance

DetailValue
Operation IDget_balance_6
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Vonage connection from the Connection dropdown.
  3. In the Operation dropdown, select get_balance_6.
  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.