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 CC Task API to Create a new Task at WxCC using a unique identifier.
|v1.2 and v1.0
|Webex Contact Center supports use of global variables and custom flow variables (local variables) while building flows for the digital channels.
|Global variables are defined in the Webex CC Admin Portal.
|Set Global Variable
|Flow variables are defined in the flow.
|Set Flow Variable
|Calls Webex CC Task API to Queue a Task.
|v1.0, v1.1, v1.2, and v1.3
|PIQ and EWT
|Provides the caller's current Position in Queue (PIQ) and the Estimated Wait Time (EWT).
|PIQ and EWT
|Calls Webex CC Task API to notify that that the task routed is accepted when the participant is added successfully.
|Calls Webex CC Task API to notify that that the task routed is rejected when adding the participant failed.
|Calls Webex CC Task API to notify that that the task modified accepted when the participant is added/removed successfully based on the context.
|Calls Webex CC Task API to notify that that the task modified rejected when adding/removing the participant failed based on the context.
|Calls Webex CC Screen pop API. While configuring flows in Webex Connect, you’d need to use this node for sending a screen pop message to the agent contact on Webex CC.
|Calls Webex CC Task API to close task directly on Webex CC.
|Closed Task on WxCC
|Calls Webex CC Task API to notify Webex CC on close task accept.
|Close Task Accept
|Calls Webex CC Task API to notify Webex CC on close task reject.
|Close Task Reject
|Calls Webex Engage Resolve Conversation API to resolve conversation on Webex Engage.
|v1.1 and v1.0
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 Cisco Webex Contact Center Task nodes (Task nodes are Create Task, Set Variable, Queue Task, PIQ and EWT, Routed Notification, Modified Notification, Screen Pop, Close Task, and Resolve Conversation).
To authorize a pre-built integration:
- Go to Assets → Integrations.
- Select Pre-built Integrations under Integration Type, to display the list of all pre-built integrations.
The integrations which are not yet authorized show the status as Pending Authorization.
- Click Actions → Manage associated with the integration you want to authorize.
- On the Manage Integrations page, scroll down to the Node Authorizations section. This section lists all the authorizations mapped to this integration.
If the integration nodes have no auth required, then it is not shown in the list.
- Click Action → Add Authorization associated with the authorization, where Auth Type is oauth2 and Status is Authorization Pending.
- Enter the Authorization Name
- Click Authorize.
A pop-up appears.
- Enter your Cisco email address and click Sign in.
The status of the authorization will change to Authorized and all the nodes under this authorization are authorized and ready for use.
Once authorized, you can perform the following actions on the authorization.
- View - allows you to view the authorization.
- Update - allows you to update the authorization details.
- Make it as default - allows you to make a particular authorization default for that node.
- Remove - allows you to delete the authorization.
If an OAuth 2.0 type authorization is edited in the Admin portal, you will be prompted to re-authorize the authorization.
You are not allowed to delete the authorization if it is mapped/used in flow assets.
Updated 8 days ago