Package com.pulumi.gcp.diagflow.inputs
Class CxFlowEventHandlerTriggerFulfillmentMessageArgs
- java.lang.Object
-
- com.pulumi.resources.InputArgs
-
- com.pulumi.resources.ResourceArgs
-
- com.pulumi.gcp.diagflow.inputs.CxFlowEventHandlerTriggerFulfillmentMessageArgs
-
public final class CxFlowEventHandlerTriggerFulfillmentMessageArgs extends com.pulumi.resources.ResourceArgs
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description static class
CxFlowEventHandlerTriggerFulfillmentMessageArgs.Builder
-
Field Summary
Fields Modifier and Type Field Description static CxFlowEventHandlerTriggerFulfillmentMessageArgs
Empty
-
Method Summary
-
-
-
Field Detail
-
Empty
public static final CxFlowEventHandlerTriggerFulfillmentMessageArgs Empty
-
-
Method Detail
-
channel
public java.util.Optional<com.pulumi.core.Output<java.lang.String>> channel()
- Returns:
- The channel which the response is associated with. Clients can specify the channel via QueryParameters.channel, and only associated channel response will be returned.
-
conversationSuccess
public java.util.Optional<com.pulumi.core.Output<CxFlowEventHandlerTriggerFulfillmentMessageConversationSuccessArgs>> conversationSuccess()
- Returns:
- Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example: * In the entryFulfillment of a Page if entering the page indicates that the conversation succeeded. * In a webhook response when you determine that you handled the customer issue. Structure is documented below.
-
liveAgentHandoff
public java.util.Optional<com.pulumi.core.Output<CxFlowEventHandlerTriggerFulfillmentMessageLiveAgentHandoffArgs>> liveAgentHandoff()
- Returns:
- Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example: * In the entryFulfillment of a Page if entering the page indicates something went extremely wrong in the conversation. * In a webhook response when you determine that the customer issue can only be handled by a human. Structure is documented below.
-
outputAudioText
public java.util.Optional<com.pulumi.core.Output<CxFlowEventHandlerTriggerFulfillmentMessageOutputAudioTextArgs>> outputAudioText()
- Returns:
- A text or ssml response that is preferentially used for TTS output audio synthesis, as described in the comment on the ResponseMessage message. Structure is documented below.
-
payload
public java.util.Optional<com.pulumi.core.Output<java.lang.String>> payload()
- Returns:
- A custom, platform-specific payload.
-
playAudio
public java.util.Optional<com.pulumi.core.Output<CxFlowEventHandlerTriggerFulfillmentMessagePlayAudioArgs>> playAudio()
- Returns:
- Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
-
telephonyTransferCall
public java.util.Optional<com.pulumi.core.Output<CxFlowEventHandlerTriggerFulfillmentMessageTelephonyTransferCallArgs>> telephonyTransferCall()
- Returns:
- Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
-
text
public java.util.Optional<com.pulumi.core.Output<CxFlowEventHandlerTriggerFulfillmentMessageTextArgs>> text()
- Returns:
- The text response message. Structure is documented below.
-
builder
public static CxFlowEventHandlerTriggerFulfillmentMessageArgs.Builder builder()
-
builder
public static CxFlowEventHandlerTriggerFulfillmentMessageArgs.Builder builder(CxFlowEventHandlerTriggerFulfillmentMessageArgs defaults)
-
-