Webex Connect offers the following nodes for Cisco Webex Contact Center integration. The node authorization configuration details are available in the next section.
|Recommended Node Version
|Calls Webex Engage Conversation Search API to search for an existing conversation using the customer identifier
|v1.0, v1.1, and v1.3
|Calls Webex Engage Append Conversation API to append a message to an existing conversation
|v1.0, v1.3, and v1.4
|Calls Webex Engage Create Conversation API to create a new conversation on Webex Engage with the channel and customer details
|v1.0, v1.2, and v1.3
|Calls Webex Engage Update Conversation API to update a new conversation on Webex Engage with the channel and customer details
|Calls Webex Engage API to add a participant to a conversation
|Calls Webex Engage API to remove a participant from a conversation
|Calls Webex Engage API to close the conversation
|Calls Webex Engage Update Conversation API to Re-open and queue a conversation which is in closed state
Client applications (in this case Webex Connect) are required to provide a valid access token for using various Cisco Webex Contact Center and imiengage APIs. The access token is generated using the authorization details configured within the ‘Node Runtime Authorization’ field that Cisco Webex Contact Center users are required to provide during flow configuration.
For all the Authorization that is being accessed by Webex Connect, if the authorizing credentials are updated in the integrating system, the Webex Connect will loose access to the integration and the users will have to re-authorize the node.
Example of Authorization Credentials are: Username, Password, Client ID, Client Secret Key, Access Key etc.
For Webex CC Engage nodes (Engage nodes are Search Conversation, Append Conversation, Create Conversation, Update Conversation, Add Participant, Remove Participant, Close Conversation, and Re-open Conversation), you’ll be asked to provide the following details on clicking + ADD NEW AUTHORIZATION option:
Here’re a brief description of the details that you need to provide:
- Authorization Name - A unique name for identifying this authorization.
Please note that the above details are provided to the requestor during the tenant provisioning process.
Click AUTHORIZE after configuring the above details. You will be redirected to Cisco Webex CC user login, where you to provide the username and password to login. You will see the confirmation message that the authorization is successfully added on the successful authorization.
Once you have successfully configured the authorization details for a node, you will be able to reuse it every time to use the same node. If you delete a node authorization, you will need to go and update the authorization configuration wherever you’d used the same node with the same authorization.
Nodes in Webex Connect have one or more outcome edges (that can be used to configure transitions to the next logical node based on the requirements) corresponding to various success or error cases. Some of the standard node outcomes include:
- onError – Request processing failed due to an error.
- onInvalidData – Request processing failed due to missing data.
- onInvalidChoice – Request processing failed but there is no outcome configured for the concerned scenario.
- onTimeout – Request processing timed out.
- onAuthorizationFailure – Request could not be processed due to authorization failure.
Apart from the standard outcomes, each node may have one or more node-specific outcomes. Descriptions for those are given below.
Updated 16 days ago