An intent represents a mapping between input from a user and an action to
| be taken by your application. When you pass user input to the
| {@link google.cloud.dialogflow.v2.Sessions.DetectIntent|DetectIntent} (or
| {@link google.cloud.dialogflow.v2.Sessions.StreamingDetectIntent|StreamingDetectIntent}) method, the
| Dialogflow API analyzes the input and searches
| for a matching intent. If no match is found, the Dialogflow API returns a
| fallback intent (is_fallback = true).
|
| You can provide additional information for the Dialogflow API to use to
| match user input to an intent by adding the following to your intent.
|
| Contexts - provide additional context for intent analysis. For
| example, if an intent is related to an object in your application that
| plays music, you can provide a context to determine when to match the
| intent if the user input is "turn it off". You can include a context
| that matches the intent when there is previous user input of
| "play music", and not when there is previous user input of
| "turn on the light".
|
| Events - allow for matching an intent by using an event name
| instead of user input. Your application can provide an event name and
| related parameters to the Dialogflow API to match an intent. For
| example, when your application starts, you can send a welcome event
| with a user name parameter to the Dialogflow API to match an intent with
| a personalized welcome message for the user.
|
| Training phrases - provide examples of user input to train the
| Dialogflow API agent to better match intents.
Don't need proejct idea if path (service accounts have projectid in them)
| * a path to a JSON file, the projectId option below is not necessary.
| * NOTE: .pem and .p12 require you to specify options.email as well.
| // A context represents additional information included with user input or with
| // an intent returned by the Dialogflow API. Contexts are helpful for
| // differentiating user input which may be vague or have a different meaning
| // depending on additional details from your application such as user setting
| // and preferences, previous user input, where the user is in your application,
| // geographic location, and so on.
```
From aog & elsewhere:
An intent represents a mapping between input from a user and an action to
| be taken by your application. When you pass user input to the | {@link google.cloud.dialogflow.v2.Sessions.DetectIntent|DetectIntent} (or | {@link google.cloud.dialogflow.v2.Sessions.StreamingDetectIntent|StreamingDetectIntent}) method, the | Dialogflow API analyzes the input and searches | for a matching intent. If no match is found, the Dialogflow API returns a | fallback intent (
is_fallback= true). | | You can provide additional information for the Dialogflow API to use to | match user input to an intent by adding the following to your intent. | | Contexts - provide additional context for intent analysis. For | example, if an intent is related to an object in your application that | plays music, you can provide a context to determine when to match the | intent if the user input is "turn it off". You can include a context | that matches the intent when there is previous user input of | "play music", and not when there is previous user input of | "turn on the light". | | Events - allow for matching an intent by using an event name | instead of user input. Your application can provide an event name and | related parameters to the Dialogflow API to match an intent. For | example, when your application starts, you can send a welcome event | with a user name parameter to the Dialogflow API to match an intent with | a personalized welcome message for the user. | | Training phrases - provide examples of user input to train the | Dialogflow API agent to better match intents.Don't need proejct idea if path (service accounts have projectid in them)