Package-level declarations
Types
Metadata for article suggestion models.
Defines the Automated Agent to connect to a conversation.
Dialogflow contexts are similar to natural language context. If a person says to you "they are orange", you need context in order to understand what "they" is referring to. Similarly, for Dialogflow to handle an end-user expression like that, it needs to be provided with context in order to correctly match an intent. Using contexts, you can control the flow of a conversation. You can configure contexts for an intent by setting input and output contexts, which are identified by string names. When an intent is matched, any configured output contexts for that intent become active. While any contexts are active, Dialogflow is more likely to match intents that are configured with input contexts that correspond to the currently active contexts. For more information about context, see the Contexts guide.
Represents metadata of a conversation.
Represents a phone number for telephony integration. It allows for connecting a particular conversation over telephony.
The status of a reload attempt.
An entity entry for an associated entity type.
The configuration for model evaluation.
Smart compose specific configuration for evaluation job.
Smart reply specific configuration for evaluation job.
Whether fulfillment is enabled for the specific feature.
Represents configuration for a generic web service. Dialogflow supports two mechanisms for authentications: - Basic authentication with username and password. - Authentication with additional authentication headers. More information could be found at: https://cloud.google.com/dialogflow/docs/fulfillment-configure.
By default, your agent responds to a matched intent with a static response. As an alternative, you can provide a more dynamic response by using fulfillment. When you enable fulfillment for an intent, Dialogflow responds to that intent by calling a service that you define. For example, if an end-user wants to schedule a haircut on Friday, your service can check your database and respond to the end-user with availability information for Friday. For more information, see the fulfillment guide.
Google Cloud Storage location for the inputs.
Custom conversation models used in agent assist feature. Supported feature: ARTICLE_SUGGESTION, SMART_COMPOSE, SMART_REPLY, CONVERSATION_SUMMARIZATION.
Config to process conversation.
Configuration for analyses to run on each conversation message.
Defines the Human Agent Assist to connect to a conversation.
Detail human agent assistant config.
Config for suggestion features.
Settings that determine how to filter recent conversation context when generating suggestions.
Dialogflow source setting. Supported feature: DIALOGFLOW_ASSIST.
Document source settings. Supported features: SMART_REPLY, SMART_COMPOSE.
Knowledge base source settings. Supported features: ARTICLE_SUGGESTION, FAQ.
Config for suggestion query.
Settings of suggestion trigger.
Configuration specific to LivePerson (https://www.liveperson.com).
Defines the hand off to a live agent, typically on which external agent service provider to connect to a conversation. Currently, this feature is not general available, please contact Google to get access.
Configuration specific to Salesforce Live Agent.
Represents the configuration of importing a set of conversation files in Google Cloud Storage.
InputDataset used to create model or do evaluation. NextID:5
Represents a single followup intent in the chain.
Opens the given URI.
The button object that appears at the bottom of a card.
The basic card message. Useful for displaying information.
Actions on Google action to open a given url.
Browsing carousel tile
Browse Carousel Card for Actions on Google. https://developers.google.com/actions/assistant/responses#browsing_carousel
Contains information about a button.
The card response message.
An item in the carousel.
The card for presenting a carousel of options to select from.
Column properties for TableCard.
The image response message.
The suggestion chip message that allows the user to jump out to the app or website associated with this agent.
An item in the list.
The card for presenting a list of options to select from.
The media content card for Actions on Google.
Response media object for media content card.
The quick replies response message.
A rich response message. Corresponds to the intent Response
field in the Dialogflow console. For more information, see Rich response messages.
Additional info about the select item for when it is triggered in a dialog.
The simple response message containing speech or text.
The collection of simple response candidates. This message in QueryResult.fulfillment_messages
and WebhookResponse.fulfillment_messages
should contain only one SimpleResponse
.
The suggestion chip message that the user can tap to quickly post a reply to the conversation.
The collection of suggestions.
Cell of TableCardRow.
Table card for Actions on Google.
Row of TableCard.
The text response message.
Represents a part of a training phrase.
Represents an example that the agent is trained on.
Defines logging behavior for conversation lifecycle events.
Defines notification behavior.
The evaluation metrics for smart reply model.
Evaluation metrics when retrieving n
smart replies with the model.
Metadata for smart reply models.
Configures speech transcription for ConversationProfile.
The type of Human Agent Assistant API suggestion to perform, and the maximum number of results to return for that type. Multiple Feature
objects can be specified in the features
list.
Configuration of how speech should be synthesized.
Description of which voice to use for speech synthesis.
The Status
type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status
message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.