Date: Fri, 29 Mar 2024 12:55:45 +0000 (UTC) Message-ID: <1154072490.3.1711716945707@9cab571c8928> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2_504734926.1711716945707" ------=_Part_2_504734926.1711716945707 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This article provides a high-level summary of the concepts a= nd benefits behind Webhooks.
Looking for specific events types and values? Just expand the = "Events" section to view the child pages.
In essence, using a webhooks framework allows Telax to expose certain ev= ents data to our partners and customers in real time. This allows us = to notify external systems of events as those events take place.
Now let's take a look at webhooks events in a specific context. As= you may be aware, the Telax desktop Call Center Agent (CCA) cl= ient uses a Cloud CRM connector. This application, prior to webhooks, recei= ved CRM events from the CCA. The connector also performs certain actions wh= en the CCA software triggers it to do so, based on an event.
These event-based actions could include but are not limited to:
Again, the previous configuration was that events were pushed from the C= CA client to the CRM connector. With the implementation of webhooks,&= nbsp;we=E2=80=99ve created a server-side application that delivers events t= o the cloud CRM connector for each account. This means events are pus= hed or "fired" from Telax servers to the external system - in this case, th= e CRM connector.