Dialogue Manager Nodes for Dialogue Studio

Dialogue Studio provided a tool for designing and programming flows. This guide will focus primarily on the Dialogue Manager Nodes.

Prerequisites

Dialogue manager configured to start with pre-queue stage, see: Dialogue Manager Pre-queue stage connection with Dialogue Studio

AnywhereNow Triggers Nodes

Icon Description

Icon	Description
	Incoming message Creates an HTTP end-point to receive messages. Configuration Key (string) -The API Key to authorize the calling application Note The API Key is configured in the Dialogue Manager, see: Plugin Settings Output Object payload (string) -Contains the body of the incoming HTTP request. Details The node will listen on the end-point `/api/v1/message` for POST requests. It validates if the HTTP Authorization header contains valid basic authentication credentials and validates the API Key. The API Key can be configured on the node itself. Note This node does not send any response to the request. The flow must include an HTTP Response node (e.g. wait for message, enqueue or disconnect) to complete the request. Important Regardless of the number of UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location. or UCC Services you use, you can only utilize one “incoming message” node per Dialogue Studio instance. Ensure that all UCCs share the same “ApiKey”.

Incoming message

Creates an HTTP end-point to receive messages.

Configuration

Key (string) -The API Key to authorize the calling application

Note

The API Key is configured in the Dialogue Manager, see: Plugin Settings

Output Object

payload (string) -Contains the body of the incoming HTTP request.

Details

The node will listen on the end-point /api/v1/message for POST requests. It validates if the HTTP Authorization header contains valid basic authentication credentials and validates the API Key.

The API Key can be configured on the node itself.

Note

This node does not send any response to the request. The flow must include an HTTP Response node (e.g. wait for message, enqueue or disconnect) to complete the request.

Important

Regardless of the number of UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location. or UCC Services you use, you can only utilize one “incoming message” node per Dialogue Studio instance. Ensure that all UCCs share the same “ApiKey”.

AnywhereNow Action Nodes

Icon	Description
	Say Creates a message. Configuration Message (string) - A message to create Output Object payload (string) - Contains the actual action type and the message. Details Different values can be used in the message Select the type and fill in the path to the wanted value. A _msgid is expected in the message that contains the ID generated by the first request node

Icon

Description

Say

Creates a message.

Configuration

Message (string) - A message to create

Output Object

payload (string) - Contains the actual action type and the message.

Details

Different values can be used in the message Select the type and fill in the path to the wanted value.

A _msgid is expected in the message that contains the ID generated by the first request node

AnywhereNow End Nodes

Icon	Description
	Wait for message Sends a response back to the request received from an HTTP Input node (incoming message). Configuration flowid (string) – Used to identify the flow. Generated by default and configurable on the node. Details The response contains all actions in the flow and the flowid The flowid can be used in a subsequent API call to DialogueStudio A _msgid is expected in the message that contains the ID generated by the first request node Note This node does not have an end-point. The flow must include an incoming message node to receive a request.
	Enqueue Sends a response back to the request received from an HTTP Input node (incoming message). Configuration flowid (string) – Used to identify the flow. Generated by default and configurable on the node. skill (string) – Used to identify the skill in which the session should be queued. If no value is specified, or the specified skill does not exist in the UCC, the plugin flow settings will be used to determine a skill and queue the session accordingly. Details The response contains all actions in the flow and the flowid The flowid can be used in a subsequent API call to DialogueStudio. A _msgid is expected in the message that contains the ID generated by the first node Note This node does not have an end-point. The flow must include an incoming message node to receive a request.
	Disconnect Sends a response back to request received from an HTTP Input node. Configuration flowid (string) – Used to identify the flow. Generated by default and configurable on the node. Details The response contains all actions in the flow and the flowid The flowid can be used in a subsequent API call to DialogueStudio. A _msgid is expected in the message that contains the ID generated by the first node Note This node does not have an end-point. The flow must include an incoming message node to receive a request.

Icon

Description

Wait for message

Sends a response back to the request received from an HTTP Input node (incoming message).

Configuration

flowid (string) – Used to identify the flow. Generated by default and configurable on the node.

Details

The response contains all actions in the flow and the flowid

The flowid can be used in a subsequent API call to DialogueStudio

A _msgid is expected in the message that contains the ID generated by the first request node

Note

This node does not have an end-point. The flow must include an incoming message node to receive a request.

Enqueue

Sends a response back to the request received from an HTTP Input node (incoming message).

Configuration

flowid (string) – Used to identify the flow. Generated by default and configurable on the node.
skill (string) – Used to identify the skill in which the session should be queued. If no value is specified, or the specified skill does not exist in the UCC, the plugin flow settings will be used to determine a skill and queue the session accordingly.

Details

The response contains all actions in the flow and the flowid

The flowid can be used in a subsequent API call to DialogueStudio.

A _msgid is expected in the message that contains the ID generated by the first node

Note

This node does not have an end-point. The flow must include an incoming message node to receive a request.

Disconnect

Sends a response back to request received from an HTTP Input node.

Configuration

flowid (string) – Used to identify the flow. Generated by default and configurable on the node.

Details

The response contains all actions in the flow and the flowid

The flowid can be used in a subsequent API call to DialogueStudio.

A _msgid is expected in the message that contains the ID generated by the first node

Note

This node does not have an end-point. The flow must include an incoming message node to receive a request.