---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up the Vonage spoke

# Set up the Vonage spoke {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read  
Integrate your ServiceNow instance with the Vonage instance to enable communication between them. With this integration, your ServiceNow instance can automate actions on the Vonage instance, while the Vonage instance can send payloads to your ServiceNow instance.

## Before you begin

* Request an Integration Hub subscription.
* Activate the Vonage spoke plugin on your ServiceNow instance.
* Role required: admin.
* Vonage developer instance account.
{#setup-vonage-spoke__ul_agy_qxd_rlb}

## Configure the Vonage developer instance {#ariaid-title2}

Generate essential credentials, such as API keys, secrets, and signature secrets, to set up your Vonage developer instance. Your ServiceNow instance uses these credentials in the connection record to connect to the Vonage developer instance.

### Before you begin

Role required: admin

Access to a Vonage developer account.

### Procedure

1. Log in to <https://developer.vonage.com/en/home>.
2. On the Vonage Developer Center page, select My dashboard.
3. On the Vonage API Dashboard page, use the default API key and the API secret or create your custom API key and API secret.
   1. To use the default API key and the API secret, copy the default API key and the API secret values.
   2. To generate a custom API key and API secret, on the left panel, select API Settings.
   3. Select Request more API keys.
   4. Fill and submit the form.
   5. Select Create new secret.
   6. In the Add a new secret window, enter your custom secret.
   7. Select Save.
   {#configure-vonage-developer-instance__substeps_zsv_zq1_5yb}
4. From the Signature secret field, copy the signature secret.

## Configure connection record for Vonage connection and credential alias {#ariaid-title3}

Configure a connection record that enables your ServiceNow instance to connect with the Vonage instance and automate various actions on the Vonage instance. For example, create a flow on Workflow Studio that gets your Vonage account balance.

### Before you begin

Role required: admin  
Note:  
Ensure that you are in the Vonage spoke scope.

### Procedure

1. Navigate to AllProcess AutomationFlow Designer.
2. Select Connections.
3. In the Search all connections field, enter <kbd class="ph userinput">Vonage</kbd>.
4. On the Vonage card, select View Details.
5. Select Configure.
6. Fill the form.  
   {#configure-connection-record-for-vonage-alias__table_vpl_zd3_5yb__entry__2}

   | Field | Description |
   |-|-|
   | Connection Name | The default and read-only name of the connection record. To provide a custom name to the connection record, create a connection record by selecting Add Connection. |
   | Connection URL | The URL to connect to the Vonage API. |
   | Messages API Version | The version of APIs the connection record requests for using the SMS feature in the Vonage instance. |
   | Voice API Version | The version of APIs the connection record requests for using the Voice feature in the Vonage instance. |
   | Credential Name | Name of the credential record. The default name os Vonage credential which you can update. |
   | Application Name | Name of the account that you had entered in the Settings page of the Vonage developers account. |
   | API Key | API key you had acquired in the Vonage developer instance. |
   | API Secret | API secret you had acquired in the Vonage developer instance. |
   | Signature Secret | Signature secret key you had acquired in the Vonage developer instance. |
   [Table 1. Create Connection]

   {#configure-connection-record-for-vonage-alias__table_vpl_zd3_5yb}
7. Select Create Connection.

## Configure connection record for Vonage Primary alias {#ariaid-title4}

Configure a connection record that enables your ServiceNow instance to connect with the Vonage instance and automate various actions on the Vonage instance. For example, create a flow on Workflow Studio that gets your Vonage account balance.

### Before you begin

Role required: admin  
Note:  
Ensure that you are in the Vonage spoke scope.

### Procedure

1. Navigate to AllProcess AutomationFlow Designer.
2. Select Connections.
3. In the Search all connections field, enter <kbd class="ph userinput">Vonage</kbd>.
4. On the VonagePrimary card, select View Details.
5. Select Configure.
6. Fill the form.  
   {#configure-connection-record-for-vonage-primary-alias__table_vpl_zd3_5yb__entry__2}

   | Field | Description |
   |-|-|
   | Connection Name | The default and read-only name of the connection record. To provide a custom name to the connection record, create a connection record by selecting Add Connection. |
   | Connection URL | The URL to connect to the Vonage API. Enter <https://rest.nexmo.com>. |
   | API Key | API key you had acquired in the Vonage developer instance. |
   | API Secret | API secret you had acquired in the Vonage developer instance. |
   [Table 2. Create Connection]

   {#configure-connection-record-for-vonage-primary-alias__table_vpl_zd3_5yb}
7. Select Create Connection.
{#configure-connection-record-for-vonage-primary-alias__steps_hft_jxd_vyb}

## Create a webhook to receive data from Vonage {#ariaid-title5}

Set up webhooks for SMS to enable the Vonage API platform to send data to your ServiceNow instance. For instance, if a flow in your ServiceNow instance sends an API request for call details to the Vonage API but the request
fails initially, the webhook ensures that the Vonage API sends the data later.

### Before you begin

Role required: admin.

### Procedure

1. Navigate to AllVonage spokeVonage webhook Registries.
2. Select New.
3. On the form, fill in these fields.  
   {#create-sms-webhook__table_smp_4jf_pmb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name to uniquely identify the webhook record. |
   | Description | Description of the webhook record. |
   | Event Type | Type of event for which the webhook is set up. Select SMS. |
   | Secret Key | Secret key to authenticate the webhook requests. Enter your custom secret key. |
   [Table 3. Vonage Webhook Registry form]

   {#create-sms-webhook__table_smp_4jf_pmb}
4. Right-click the form header and select Save.
5. Select Callback URL.  
   The system displays the webhook callback URL.
6. Copy and record the webhook callback URL.
7. Log in to <https://developer.vonage.com/en/home>.
8. On the left panel, under Build \& Manage, select Applications.
9. On the Your applications page, select the menu icon (![Menu icon.]()) for your application.
10. Select Edit.
11. Under the Messages heading, enter the callback URL in the Inbound URL and the Status URL fields.
12. On the left panel, select API Settings.
13. On the Settings page, under SMS Settings heading, make sure that you've selected SMS API.
14. Fill the values.  
    {#create-sms-webhook__table_r5h_wkf_pmb__entry__2}

    | Field | Value |
    |-|-|
    | Delivery receipts (DLR) webhooks | Webhook callback URL |
    | Inbound SMS webhooks | Webhook callback URL |
    [ ]

    {#create-sms-webhook__table_r5h_wkf_pmb}
15. Select Save changes.  
    SMS settings for the application are saved.

## Customize webhooks and routing policies {#ariaid-title6}

Customise the webhook routing policy and subflow as per your requirement.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllFlow DesignerDesigner.
2. Click Subflows.
3. Create a copy of the required default subflow.
4. Customize the subflow as per your requirement and publish it.  
   See [Building subflows](https://www.servicenow.com/docs/access?context=subflows&version=brazil&pubname=brazil-build-workflows&ft:locale=en-US) for more information about creating and using subflows and [Vonage Spoke](https://www.servicenow.com/docs/dvQZSxVr3X9Li9xaEv0FgA "Manage communications through calls, SMS, and WhatsApp by using the Vonage account from your ServiceNow instance.") for information about the fields that the default routing policy and subflows support.
5. Navigate to Vonage SpokeVonage WebHook Routing Policy.
6. Click New.
7. On the form, fill in the fields.  
   {#cust-routing-vonage__table_awj_xgv_z3b__entry__2}

   | Field | Description |
   |-|-|
   | Label | Unique label to identify the routing policy. |
   | Default answer | Option to specify if this is the default answer. The default answer is applicable when the conditions are not met. 1. Click the lookup icon (![Lookup icon]()). 2. Select the required subflow from the Document list. Note: Ensure that the Table name is <kbd class="ph userinput">Flow [sys_hub_flow]</kbd>. {#cust-routing-vonage__ol_sdf_ftb_1jb} |
   | Condition | Conditions to be met when the required events occur in Vonage. The supported Vonage fields are: * Keywords * Call Direction * Call Status * Event Type * From * SMS Status * SMS Text * To * WhatsApp Message Status * WhatsApp Text * Show Related Fields {#cust-routing-vonage__ul_yks_qpf_pmb} |
   | Answer | Subflow that must be triggered when the specified conditions are met. |
   [Table 4. Decision form]

   {#cust-routing-vonage__table_awj_xgv_z3b}
8. Click Submit.  
   Note:  
   These routing policies are saved in the Decision tables. Users are cautioned against directly updating or modifying data in these tables.
{#cust-routing-vonage__steps_vjr_z4f_pmb}

*[\>]: and then