Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scroll export button
scopecurrent
template-id0fa09813-8b86-460a-aa1d-ef450a80e9ce
quick-starttrue
add-onScroll PDF Exporter

Info

This guide explains how to configure Webhook integration with third-party web applications and services, for sending events related to calls.

Created: August 2023

Updated: December 2023

Permalink: https://wildix.atlassian.net/wiki/x/AYCODg

Table of Contents

Introduction

Webhook integration (currently, in Beta) allows to connect different third-party web applications and services by sending events related to calls.  

Requirements 

  • WMS 6.03
  • Cloud Analytics enabled in WMS -> PBX -> Features (it is activated by default if a PBX or whole WMS Network are running in the Cloud). 
    For more details, see documentation WMS Settings Menu - Admin Guide (see the Features section).

How to configure the integrationthe integration

1. Go to WMS -> PBX -> Integrations -> Calendars stab (or to x-bees tab in case of a PBX with x-bees licence)

2. Click on the Webhook integration -> click Install 

3. On the Connect integration screen, fill out the following fields:

Select transmission type for sending the events:

  • WebHook: POST requests are sent to the URL, specified by customer
  • AWS SQS: events are sent to AWS SQS queue


a) In case of WebHook transmission type:

  1. In the Target field, indicate the URL where the data should be sent to. 
  2. Secret is generated automatically and cannot be edited. 
  3. Choose type of events: 
    1. Call start
    2. Call update
    3. Call end


b) In case of SQS transmission type:

  1. In the Target field, indicate the SQS URL where the data should be sent to.
  2. Enter SQS Key and Secret in the relevant fields. 
  3. Choose type of events: 
    1. Call start
    2. Call update
    3. Call end

4. Click Install.

Once installed, you can see details about the new integration which includes Integration ID, Transmission type, URL, Secret, and types of events selected. 

Note

Note: Editing of the integration is currently not supported. If you need to update any data, please delete the current Webhook integration and create a new one. 


Copy the Integration ID and use it in your web application / service.

Warning

Important: The timeout for Webhook reply is 5 seconds. 


Warning

Important: For security reasons, it is highly recommended that you validate the data received to your web application / service and make sure the data comes from Wildix and the data is not broken. 

For this, check `signature` for all received events:

  • For webhook transport, you can find signature in the request's header x-signature
  • For SQS transport, you can find signature in the MessageAttributes ['X-SIGNATURE']

Configuration example

See Webhook configuration example on this page.



...

Below you can find some examples of Webhook integration usage:

  • CRM Integration

You can integrate the Webhook to automatically log and update customer call details in the CRM system. This can helps in maintaining accurate customer records and improve follow-up processes.

  • Marketing automation

You can trigger marketing automation campaigns based on call events. For example, you can send follow-up emails or SMS messages when a call ends, which could help to nurture leads and provide better customer support.

  • Customer feedback and surveys

After a call ends, the Webhook can trigger the delivery of customer satisfaction surveys or feedback requests. This helps businesses to gather valuable input for improving the service in future.

  • Ticketing system integration

You can automatically generate support tickets or service requests when a call starts or ends, which would streamline the customer support processes.

  • Custom notifications

You can set up customized notifications based on call events. For example, you can receive an SMS alert when a high-priority call starts or when a call remains on hold for too long.

...