Nodes and actions
Describes the relationship between nodes in the dialog flow and what appears in ExecuteResponse actions.
This section provides more detailed information about different types of actions that can appear in the response payloads of the API. Actions correspond to nodes in your dialog design and tell the client application what to do to continue the flow of the dialog.
Describes the relationship between nodes in the dialog flow and what appears in ExecuteResponse actions.
Message actions indicate that a message should be played to the user.
Question and answer actions prompt a user to provide text or speech input.
Data access actions tell the client app that the dialog needs more data to continue.
Continue actions help client apps smooth over delays while DLGaaS accesses external data.
Transfer external actions send an Escalation action, for example, to an IVR agent.
End external actions indicate the end of the dialog.