Routed Notification
Understand the various routed notifications types present and how they can be configured
This node calls Webex CC Routed Notification API to notify Webex CC whether adding an agent or participant to the conversation was successful or not. 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 Name | Output Variables | Node Outcomes |
|---|---|---|
| Routed Accepted | None | onInvalidData onError onInvalidChoice onauthorizationfail onTaskRoutedFailure onTaskRouted * onTimeout |
| Channel | Field Value |
|---|---|
| All channels | TASK 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 Variables | Output Variables | Versions |
|---|---|---|
| TASK ID - $(n2.webex.ID) > _ ID from the output variables of the routed event is the task IDID - $(n2.webex.ID) > > _ ID from the output variables of the routed event is the task IDAGENT ID - $(n2.webex.agentId) > > _ AgentId from the output variables of the routed event is the Agent IDQUEUE ID - $(n2.webex.queue) > > _ Queue from the output variables of the routed event is the Queue IDMEDIA RESOURCE ID - $(mediaResourceId) > > _ MediaResourceId from the output variables of the routed event is the Media Resource IDMEDIA TYPE - $(n2.webex.mediaType) > > _ MediaType from the output variables of the routed event is the Media Type | None | v1.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 Name | Output Variables | Node Outcomes |
|---|---|---|
| Routing Reject | None | onInvalidData onError onInvalidChoice onauthorizationfail onTaskRoutedFailure onTaskRouted * onTimeout |
| Channel | Field Value |
|---|---|
| All channels | TASK 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 Variables | Output Variables |
|---|---|
| TASK ID - $(n2.webex.ID) > _ ID from the output variables of the routed event is the task IDID - $(n2.webex.ID) > > _ ID from the output variables of the routed event is the task IDAGENT ID - $(n2.webex.agentId) > > _ AgentId from the output variables of the routed event is the Agent IdQUEUE ID - $(n2.webex.queue) > > _ Queue from the output variables of the routed event is the Queue IDMEDIA RESOURCE ID - $(mediaResourceId) > > _ MediaResourceId from the output variables of the routed event is the Media Resource IDMEDIA TYPE - $(n2.webex.mediaType) > > _ MediaType from the output variables of the routed event is the Media TypeREASON - $(description) > > _ $(description) will have the add participant failure reasonREASON 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).
Updated 4 days ago