Package-level declarations
Types
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 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.
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.
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 Assistant 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 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
Optional. 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.
Rich Business Messaging (RBM) Media displayed in Cards The following media-types are currently supported: Image Types * image/jpeg * image/jpg' * image/gif * image/png Video Types * video/h263 * video/m4v * video/mp4 * video/mpeg * video/mpeg4 * video/webm
Rich Business Messaging (RBM) Card content
Carousel Rich Business Messaging (RBM) rich card. Rich cards allow you to respond to users with more vivid content, e.g. with media and suggestions. If you want to show a single card with more control over the layout, please use RbmStandaloneCard instead.
Standalone Rich Business Messaging (RBM) rich card. Rich cards allow you to respond to users with more vivid content, e.g. with media and suggestions. You can group multiple rich cards into one using RbmCarouselCard but carousel cards will give you less control over the card layout.
Opens the user's default dialer app with the specified phone number but does not dial automatically.
Opens the user's default web browser app to the specified uri If the user has an app installed that is registered as the default handler for the URL, then this app will be opened instead, and its icon will be used in the suggested action UI.
Opens the device's location chooser so the user can pick a location to send back to the agent.
Rich Business Messaging (RBM) suggested client-side action that the user can choose from the card.
Rich Business Messaging (RBM) suggested reply that the user can click instead of typing in their own response.
Rich Business Messaging (RBM) suggestion. Suggestions allow user to easily select/click a predefined response or perform an action (like opening a web uri).
Rich Business Messaging (RBM) text response with suggestions.
Corresponds to the Response
field in the Dialogflow console.
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.
Plays audio from a file in Telephony Gateway.
Synthesizes speech and plays back the synthesized audio to the caller in Telephony Gateway. Telephony Gateway takes the synthesizer settings from DetectIntentResponse.output_audio_config
which can either be set at request-level or can come from the agent-level synthesizer config.
Transfers the call in Telephony Gateway.
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.
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.