[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-09 (世界標準時間)。"],[[["Custom events are user-defined actions that occur outside of direct end-user conversation, such as button clicks or time-based triggers."],["These custom events can be invoked either through fulfillment or via the API's `detectIntent` call, using the `queryInput.event` field."],["When invoking events with fulfillment, the `followupEventInput` field of the `WebhookResponse` is used, allowing for the specification of event names, optional parameters, and the language code."],["Upon receiving a webhook response with a custom event, Dialogflow triggers the corresponding intent, essentially redirecting the conversation flow to a new intent, ignoring any other fields in the response."],["Chaining multiple intents is possible, as a triggered intent can also invoke another event via fulfillment, but this chaining is limited to a maximum of three intent matches, where each webhook response must adhere to timeout restrictions."]]],[]]