Flow is the Schema for the Flows API. Flows represents the conversation flows when you build your chatbot agent.
Type
CRD
Group
dialogflowcx.gcp.upbound.io
Version
v1beta1
apiVersion: dialogflowcx.gcp.upbound.io/v1beta1
kind: Flow
FlowSpec defines the desired state of Flow
No description provided.
A flow's event handlers serve two purposes: They are responsible for handling events (e.g. no match, webhook errors) in the flow. They are inherited by every page's [event handlers][Page.event_handlers], which can be used to handle common events regardless of the current page. Event handlers defined in the page have higher priority than those defined in the flow. Unlike transitionRoutes, these handlers are evaluated on a first-match basis. The first one that matches the event get executed, with the rest being ignored. Structure is documented below.
The fulfillment to call when the event occurs. Handling webhook errors with a fulfillment enabled with webhook could cause infinite loop. It is invalid to specify such fulfillment for a handler handling webhooks. Structure is documented below.
NLU related settings of the flow. Structure is documented below.
Reference to a Agent in dialogflowcx to populate parent.
Policies for referencing.
Selector for a Agent in dialogflowcx to populate parent.
Policies for selection.
A flow's transition route group serve two purposes: They are responsible for matching the user's first utterances in the flow. They are inherited by every page's [transition route groups][Page.transition_route_groups]. Transition route groups defined in the page have higher priority than those defined in the flow. Format:projects//locations//agents//flows//transitionRouteGroups/.
A flow's transition routes serve two purposes: They are responsible for matching the user's first utterances in the flow. They are inherited by every page's [transition routes][Page.transition_routes] and can support use cases such as the user saying "help" or "can I talk to a human?", which can be handled in a common way regardless of the current page. Transition routes defined in the page have higher priority than those defined in the flow.
The fulfillment to call when the condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
FlowStatus defines the observed state of Flow.
No description provided.
A flow's event handlers serve two purposes: They are responsible for handling events (e.g. no match, webhook errors) in the flow. They are inherited by every page's [event handlers][Page.event_handlers], which can be used to handle common events regardless of the current page. Event handlers defined in the page have higher priority than those defined in the flow. Unlike transitionRoutes, these handlers are evaluated on a first-match basis. The first one that matches the event get executed, with the rest being ignored. Structure is documented below.
The fulfillment to call when the event occurs. Handling webhook errors with a fulfillment enabled with webhook could cause infinite loop. It is invalid to specify such fulfillment for a handler handling webhooks. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
A collection of text responses.
A flow's transition routes serve two purposes: They are responsible for matching the user's first utterances in the flow. They are inherited by every page's [transition routes][Page.transition_routes] and can support use cases such as the user saying "help" or "can I talk to a human?", which can be handled in a common way regardless of the current page. Transition routes defined in the page have higher priority than those defined in the flow.
The fulfillment to call when the condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
A collection of text responses.
Conditions of the resource.
flow
apiVersion: dialogflowcx.gcp.upbound.io/v1beta1
kind: Flow
metadata:
annotations:
meta.upbound.io/example-id: dialogflowcx/v1beta1/flow
labels:
testing.upbound.io/example-name: flow
name: flow
spec:
forProvider:
description: Test Flow
displayName: MyFlow
eventHandlers:
- event: custom-event
triggerFulfillment:
- messages:
- text:
- text:
- I didn't get that. Can you say it again?
returnPartialResponses: false
- event: sys.no-match-default
triggerFulfillment:
- messages:
- text:
- text:
- Sorry, could you say that again?
returnPartialResponses: false
- event: sys.no-input-default
triggerFulfillment:
- messages:
- text:
- text:
- One more time?
returnPartialResponses: false
nluSettings:
- classificationThreshold: 0.3
modelType: MODEL_TYPE_STANDARD
parentSelector:
matchLabels:
testing.upbound.io/example-name: flow
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.