---
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 a bi-directional webhook for the Plivo spoke

# Set up a bi-directional webhook for the Plivo spoke {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Configure a webhook to subscribe to your Plivo account with a ServiceNow callback URL.

## Before you begin

* Request Integration Hub subscription.
* Activate the Plivo spoke.
* [Set up the Plivo spoke](https://www.servicenow.com/docs/RXTmY1YPc4GJPx2F2uLBUA#plivo-setup "Integrate the ServiceNow instance and Plivo account by using the basic authentication to authenticate ServiceNow requests.")
* Role required: sn_plivo_spoke.Plivo_Admin and decision_table_admin.
{#setup-plivo-webhook__ul_xl3_c55_z3b}

## Register a Plivo webhook in ServiceNow {#ariaid-title2}

Register a Plivo webhook in your ServiceNow instance to notify the ServiceNow app when certain events occur in Plivo.

### Before you begin

Role required: sn_plivo_spoke.Plivo_Admin and decision_table_admin

### Procedure

1. Navigate to AllPlivo SpokePlivo Webhook Registries.
2. Click New.
3. On the form, fill in the fields.  
   {#create-plivo-whregistry__table_w1l_s55_z3b__entry__2}

   | Field | Description |
   |-|-|
   | Name | Unique name to identify the record. For example, <kbd class="ph userinput">Plivo webhook</kbd>. |
   | Description | Description of the record. |
   | Path | Plivo webhook path. By default, this path is set to <kbd class="ph userinput">api/sn_plivo_spoke/plivo_webhook_handler/wh_entry</kbd>. |
   [Table 1. Plivo Webhook Registry form]

   {#create-plivo-whregistry__table_w1l_s55_z3b}
4. Right-click the form header and click Save.
5. Click Callback URL.  
   The system displays the webhook callback URL.
6. Copy and record the webhook callback URL.

### Result

The Plivo webhook is registered in your ServiceNow instance.

## Add a callback URL in Plivo {#ariaid-title3}

Provide a webhook callback URL in your Plivo account to create a webhook.

### Before you begin

Role required: sn_plivo_spoke.Plivo_Admin and decision_table_admin

### Procedure

1. Log in to your Plivo console.
2. Create an application in the Plivo console as per your requirement.  
   For more information about creating an application in the Plivo console, see the Create an Application section in the [Make your first Outbound Call](https://www.plivo.com/docs/voice#make-your-first-outbound-call) page of the [Plivo documentation](https://www.plivo.com/docs/). You can also refer to the [Plivo Application documentation](https://www.plivo.com/docs/account/api/application/) for more information about creating and updating an application using Plivo APIs.
3. Enter the webhook callback URL in MESSAGE URL and ANSWER URL, and configure the application as per your requirement.

### Result

The callback URL is added in your Plivo account. You can create routing policies and subflows as per your requirement. See [Create routing policy and customize webhook](https://www.servicenow.com/docs/Ip0aTvfUUB93cxv~RovWdA#cust-webhook-plivo "Create a webhook routing policy and subflow as per your requirement.") for information regarding the creation of new routing policies and subflows.

## Create routing policy and customize webhook {#ariaid-title4}

Create a webhook routing policy and subflow as per your requirement.

### Before you begin

Role required: sn_plivo_spoke.Plivo_Admin and decision_table_admin

### About this task

Routing policy in the Plivo WebHook Routing Policy module triggers the subflows and notifies the ServiceNow instance when certain events occur in your Plivo account. See [Plivo Spoke](https://www.servicenow.com/docs/6Ir4r2rdG2SfALD37l8vrQ "Enable communications with your customers using the Plivo platform from your ServiceNow instance.") for information about the fields that the routing policy and subflows support.

### Procedure

1. Navigate to AllFlow DesignerDesigner.
2. Click Subflows.
3. Create a copy of the default subflow.  
   Two subflows are available along with Plivo spoke; Plivo Call Handler and Plivo SMS Handler. You can create a copy of either of these subflows as per your requirement.
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 [Plivo Spoke](https://www.servicenow.com/docs/6Ir4r2rdG2SfALD37l8vrQ "Enable communications with your customers using the Plivo platform from your ServiceNow instance.") for information about the supported fields.
5. Navigate to Plivo SpokePlivo WebHook Routing Policy.
6. Click New.
7. On the form, fill in the fields.  
   {#cust-webhook-plivo__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-webhook-plivo__ol_sdf_ftb_1jb} |
   | Condition | Conditions to be met when the required events occur in Plivo. |
   | Answer | Subflow that must be triggered when the specified conditions are met. |
   [Table 2. Decision form]

   {#cust-webhook-plivo__table_awj_xgv_z3b}  
   Routing policies and subflows support these Plivo fields:
   * Keywords
   * Call Event
   * Caller Name
   * Event Type
   * SMS Text
   * To Number
   * Show Related Fields
   {#cust-webhook-plivo__ul_azx_31f_3mb}
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-webhook-plivo__steps_zrl_vdf_3mb}

### Result

The routing policy and subflow are created.

*[\>]: and then


