public sealed class EventInput : IMessage<EventInput>, IEquatable<EventInput>, IDeepCloneable<EventInput>, IBufferMessage, IMessage
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?".
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.
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:
MapKey type: string
MapKey value: parameter name
MapValue type:
If parameter's entity type is a composite entity: map
Else: depending on parameter value type, could be one of string,
number, boolean, null, list or map
MapValue value:
If parameter's entity type is a composite entity:
map from composite entity property names to property values
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eEventInput\u003c/code\u003e class enables intent matching via event names, replacing natural language input for triggering specific responses in Dialogflow.\u003c/p\u003e\n"],["\u003cp\u003eVersion 4.26.0 is the latest version of the \u003ccode\u003e/dotnet/docs/reference/Google.Cloud.Dialogflow.V2/EventInput\u003c/code\u003e library, with a list of versions going back to 3.2.0.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eEventInput\u003c/code\u003e class implements interfaces like \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, supporting various functionalities for handling event data.\u003c/p\u003e\n"],["\u003cp\u003eKey properties of the \u003ccode\u003eEventInput\u003c/code\u003e class include \u003ccode\u003eLanguageCode\u003c/code\u003e, \u003ccode\u003eName\u003c/code\u003e, and \u003ccode\u003eParameters\u003c/code\u003e, which define the query's language, event identifier, and associated parameters, respectively.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eEventInput\u003c/code\u003e allows for creating personalized responses by using parameters within an event, demonstrated by an example that uses the parameter "name" in the response.\u003c/p\u003e\n"]]],[],null,[]]
