Events allow for matching intents by event name instead of the natural language input. For instance, input <event: { name: "welcome_event",
parameters: { name: "Sam" } }>
can trigger a personalized welcome response. The parameter name
may be used by the agent in the response: "Hello #welcome_event.name! What can I do for you today?"
.
JSON representation |
---|
{ "name": string, "parameters": { object }, "languageCode": string } |
Fields | |
---|---|
name |
Required. The unique identifier of the event. |
parameters |
The collection of parameters associated with the event. Depending on your protocol or client library language, this is a map, associative array, symbol table, dictionary, or JSON object composed of a collection of (MapKey, MapValue) pairs:
|
languageCode |
Required. The language of this query. See Language Support for a list of the currently supported language codes. Note that queries in the same session do not necessarily need to specify the same language. This field is ignored when used in the context of a |