Routed Notification

This node calls Webex CC Routed Notification API to notify Webex CC about the success/failure in adding an agent/participant to the conversation. While configuring flows in Webex Connect, you’d need to use this node for notifying Webex CC about the participant/agent addition to conversation.

Authorization

Refer to section Node Authorizations for more information.

Methods and Outcomes

Here’s a brief description of various methods, and corresponding output variables and node outcomes associated with each of the methods.

Method Name - Routed Accept

Method NameOutput VariablesNode Outcomes
Routed AcceptedNone onInvalidData
onError
onInvalidChoice
onauthorizationfail
onTaskRoutedFailure
onTaskRouted
* onTimeout
ChannelField Value
All channelsTASK ID - $(n2.webex.ID)
ID - $(n2.webex.ID)
AGENT ID - $(n2.webex.agentId)
QUEUE ID - $(n2.webex.queue)
MEDIA RESOURCE ID - $(mediaResourceId)
MEDIA TYPE - $(n2.webex.mediaType)
Input VariablesOutput VariablesVersions
TASK ID - $(n2.webex.ID)
>_ ID from the output variables of the routed event is the task ID

ID - $(n2.webex.ID)
>_ ID from the output variables of the routed event is the task ID

AGENT ID - $(n2.webex.agentId)
>_ AgentId from the output variables of the routed event is the Agent ID

QUEUE ID - $(n2.webex.queue)
>_ Queue from the output variables of the routed event is the Queue ID

MEDIA RESOURSE ID - $(mediaResourceId)
>_ MediaResourceId from the output variables of the routed event is the Media Resource ID

MEDIA TYPE - $(n2.webex.mediaType)
>_ MediaType from the output variables of the routed event is the Media Type
Nonev1.1 and v1.0

📘

Note:

When the variable is selected from the previous node output variables, the nodetid will be the prefix for the variable. Eg., sms.serviceNumber is an output variable of start node (node id 2), then the variable becomes $(n2.sms.serviceNumber)

Routed Rejected

Method Name - Routed Reject

Method NameOutput VariablesNode Outcomes
Routing RejectNone onInvalidData
onError
onInvalidChoice
onauthorizationfail
onTaskRoutedFailure
onTaskRouted
* onTimeout
ChannelField Value
All channelsTASK ID - $(n2.webex.ID)
ID - $(n2.webex.ID)
AGENT ID - $(n2.webex.agentId)
QUEUE ID - $(n2.webex.queue)
MEDIA RESOURCE ID - $(mediaResourceId)
MEDIA TYPE - $(n2.webex.mediaType)
REASON - $(description)
REASONCODE - $(code)
Input VariablesOutput Variables
TASK ID - $(n2.webex.ID)
>_ ID from the output variables of the routed event is the task ID

ID - $(n2.webex.ID)
>_ ID from the output variables of the routed event is the task ID

AGENT ID - $(n2.webex.agentId)
>_ AgentId from the output variables of the routed event is the Agent Id

QUEUE ID - $(n2.webex.queue)
>_ Queue from the output variables of the routed event is the Queue ID

MEDIA RESOURSE ID - $(mediaResourceId)
>_ MediaResourceId from the output variables of the routed event is the Media Resource ID

MEDIA TYPE - $(n2.webex.mediaType)
>_ MediaType from the output variables of the routed event is the Media Type

REASON - $(description)
>_ $(description) will have the add participant failure reason

REASON CODE - $(code)
>_ $(code) will have the add participant failure reason code
None

📘

Note

When the variable is selected from the previous node output variables, the node Id will be the prefix for the variable. For example, if sms.serviceNumber is an output variable of start node (node Id 2), then the variable becomes $(n2.sms.serviceNumber).