Class ConversationsGrpc.ConversationsBlockingStub

  • Enclosing class:
    ConversationsGrpc

    public static final class ConversationsGrpc.ConversationsBlockingStub
    extends io.grpc.stub.AbstractBlockingStub<ConversationsGrpc.ConversationsBlockingStub>
    A stub to allow clients to do synchronous rpc calls to service Conversations.
     Service for managing
     [Conversations][google.cloud.dialogflow.v2beta1.Conversation].
     
    • Method Detail

      • createConversation

        public Conversation createConversation​(CreateConversationRequest request)
         Creates a new conversation. Conversations are auto-completed after 24
         hours.
         Conversation Lifecycle:
         There are two stages during a conversation: Automated Agent Stage and
         Assist Stage.
         For Automated Agent Stage, there will be a dialogflow agent responding to
         user queries.
         For Assist Stage, there's no dialogflow agent responding to user queries.
         But we will provide suggestions which are generated from conversation.
         If
         [Conversation.conversation_profile][google.cloud.dialogflow.v2beta1.Conversation.conversation_profile]
         is configured for a dialogflow agent, conversation will start from
         `Automated Agent Stage`, otherwise, it will start from `Assist Stage`. And
         during `Automated Agent Stage`, once an
         [Intent][google.cloud.dialogflow.v2beta1.Intent] with
         [Intent.live_agent_handoff][google.cloud.dialogflow.v2beta1.Intent.live_agent_handoff]
         is triggered, conversation will transfer to Assist Stage.
         
      • completeConversation

        public Conversation completeConversation​(CompleteConversationRequest request)
         Completes the specified conversation. Finished conversations are purged
         from the database after 30 days.
         
      • listMessages

        public ListMessagesResponse listMessages​(ListMessagesRequest request)
         Lists messages that belong to a given conversation.
         `messages` are ordered by `create_time` in descending order. To fetch
         updates without duplication, send request with filter
         `create_time_epoch_microseconds >
         [first item's create_time of previous request]` and empty page_token.