One thing worth pointing out re: data actions is that they're intended to abstract the specifics of interacting away from the call flow itself. Within the flow, you only need to work with the contract of the data action; this becomes a simple input/output form that should be easy to interpret within the call flow itself. The specifics of the external API are contained inside the data action configuration. This allows the person building the caller experience to focus on that part of the process, and allow someone better versed in dealing with APIs to help build out the data action.
There are threads both here in the community and in the developer forum (https://developer.mypurecloud.com/forum/) regarding data actions that might be helpful.
------------------------------
Richard Schott
Genesys - Employees
------------------------------
Original Message:
Sent: 04-09-2020 10:36
From: Roberto Vallejo
Subject: Web Services
Thank you!
------------------------------
Ling. Roberto Vallejo
Sixbell México
Original Message:
Sent: 04-09-2020 08:45
From: Richard Schott
Subject: Web Services
As in calling some other system's web service endpoints to use that information within your call flow? If so, then yes; that whole process is handled by a data action: https://help.mypurecloud.com/articles/about-the-data-actions-integrations/.
------------------------------
Richard Schott
Genesys - Employees
Original Message:
Sent: 04-08-2020 16:38
From: Roberto Vallejo
Subject: Web Services
Does anyone knows if its possible to use web services in architect?
Kind regards!
#ArchitectureandDesign
------------------------------
Ling. Roberto Vallejo
Sixbell México
------------------------------