Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Vonage Spoke

Manage communications through calls, SMS, and WhatsApp by using the Vonage account from your ServiceNow instance.

Request apps on the Store

Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

Integration Hub subscription

This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.

Spoke version

Vonage spoke v2.1.0 is the latest version.

Supported versions

This spoke was built for Vonage for these versions, but may be compatible with later versions:

  • Messages API version v1
  • Voice API version v1

Spoke requirements

Spoke dependencies

If you’re having trouble installing the app, ensure that these dependent plugins are installed:

  • ServiceNow IntegrationHub Action Step - REST (com.glide.hub.action_step.rest)
  • ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime)
  • Complex Object (com.glide.cobject)
  • ServiceNow Flow Designer - Dynamic Inputs (com.glide.hub.dynamic_inputs)

Note: Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation.

Spoke subflows

The Vonage spoke provides sample subflows to demonstrate automating Vonage tasks. To customize a sample subflow, copy it to a new application scope. Available sample subflows include:

SubflowDescription
Vonage SMS WebhookProcesses the SMS requests from Vonage.
Vonage Voice WebhookProcesses the voice requests from Vonage.
Vonage WhatsApp WebhookProcesses the WhatsApp requests from Vonage.

To customize the default subflow, you must a create a copy of the sample subflow and customize the subflow as per your requirement. While customizing subflows, you must ensure that the subflows are configured to avoid infinite loops.

Spoke triggers

Use triggers in the Vonage spoke to subscribe to the required events. The endpoint enables webhooks to connect with your ServiceNow instance. You can configure the flows to execute only when the specified trigger conditions are met. The supported events are:

CategoryTriggerDescription
Call ManagementVoice RingingTrigger is initiated when a call is made from Vonage and the number is Ringing.
Voice AnsweredTrigger is initiated when a call is made from Vonage and the call is Answered.
Voice CompletedTrigger is initiated when a call is made from Vonage and the call is Completed.
SMS ManagementSMS DeliveredTrigger is initiated when an SMS is sent from Vonage to a number.
SMS FailedTrigger is initiated when an SMS is sent from Vonage and it fails.
SMS AcceptedTrigger is initiated when a message has been accepted for delivery, but has not yet delivered.

For information about setting up the triggers for the Vonage spoke, see Setup the trigger for vonage spoke.

Spoke actions

The Vonage spoke provides actions to automate Vonage tasks when events occurs in your ServiceNow instance. Available actions include:

CategoryActionDescription
Account ManagementGet Account BalanceRetrieves the current balance of the Vonage account.
Call ManagementPlay DTMF tone into CallPlays DTMF \(Dual-tone multi-frequency\) tones into an active call
Attach Recording To ServiceNow RecordAttaches a call recording to the target ServiceNow record.
Create Outbound CallCreates an outbound call to a phone number.
Generate NCCOConstructs a Nexmo Call Control Objects \(NCCO\) that is used in Create an Outbound Call action.
Generate Connect NCCOGenerates a Nexmo Call Control Object \(NCCO\) that defines how to connect an outbound call to endpoints such as a phone number or WebSocket.
Generate Notify NCCOGenerates a Nexmo Call Control Object \(NCCO\) that defines a notify action for an outbound call.
Generate Transfer NCCOGenerates a Nexmo Call Control Object \(NCCO\) that defines how to transfer an active call.
Look Up Call DetailsRetrieves the details of the specified call.
Look up CallsRetrieves details of the specified calls.
Play Audio into CallPlays an audio file into an active call.
Play Text to Speech into CallPlays text-to-speech into an active call.
Stop Playing Audio into CallStops playing an audio file into an active call.
Stop Text to Speech In CallStops text-to-speech into an active call.
Update CallUpdates the status of an active call.
Number ManagementLook up NumbersRetrieves all the inbound numbers associated with the Vonage account.
RCS ManagementNote: If you are upgrading from an earlier version of the spoke, make sure to generate a new JWT token in your existing credential record before using this category actions.Send RCS Card MessageSends an RCS \(Rich Communication Services\) card message to a specified phone number.
Send RCS Media MessageSends an RCS \(Rich Communication Services\) media message to a specified phone number.
Send RCS Text MessageSends an RCS \(Rich Communication Services\) text message to a specified phone number.
SMS ManagementSend SMSSends an SMS \(Short Message Service\) to a phone number.
WhatsApp ManagementNote: If you are upgrading from an earlier version of the spoke, make sure to generate a new JWT token in your existing credential record before using this category actions.Send ContactsSends contacts to a WhatsApp number.
Send LocationSends geographic coordinates of a location to a WhatsApp number.
Send Media MessageSends a media message to a WhatsApp number.
Send Text MessageSends a text message to a WhatsApp number.
Send Text Message Using TemplateSends a text message using the template to a WhatsApp number.

Spoke module

Bi-directional webhooks can be set up to be notified about the required events. Routing policy defines conditions that must be met to notify the ServiceNow instance. These conditions are based on the events in Vonage that you want to be notified about. When the conditions are met, routing policy triggers the associated subflow, which in turn automates the Vonage tasks. By default, the Vonage Spoke application is available and has the following modules:

  • Vonage Webhook Registries
  • Vonage WebHook Routing Policies

Use the Vonage Webhook Registries module to assign a token and provide the API path. You must generate a Callback URL here and provide this URL in Vonage. Default routing policies are provided as a reference in the Vonage WebHook Routing Policies module. Customize these routing policies as per your requirement. The routing policy supports these fields:

  • Keywords
  • Call Direction
  • Call Status
  • Event Type
  • From
  • SMS Status
  • SMS Text
  • To
  • WhatsApp Message Status
  • WhatsApp Text
  • Show Related Fields

Connection and credential alias requirements

Integration Hub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection. For more information, see Connections and Credentials.

Two connection and credential aliases are available along with the Vonage spoke:

Vonage aliasDescription
VonagePrimaryRequired for the actions that manage SMS, number, and account.
VonageRequired for the actions that manage calls and WhatsApp.

For information about setting up the spoke, see Set up the Vonage spoke.