import * as pulumi from "@pulumi/pulumi"; import { input as inputs, output as outputs } from "../../types"; /** * Creates a flow in the specified agent. */ export declare class AgentFlow extends pulumi.CustomResource { /** * Get an existing AgentFlow resource's state with the given name, ID, and optional extra * properties used to qualify the lookup. * * @param name The _unique_ name of the resulting resource. * @param id The _unique_ provider ID of the resource to lookup. * @param opts Optional settings to control the behavior of the CustomResource. */ static get(name: string, id: pulumi.Input, opts?: pulumi.CustomResourceOptions): AgentFlow; /** * Returns true if the given object is an instance of AgentFlow. This is designed to work even * when multiple copies of the Pulumi SDK have been loaded into the same process. */ static isInstance(obj: any): obj is AgentFlow; /** * The description of the flow. The maximum length is 500 characters. If exceeded, the request is rejected. */ readonly description: pulumi.Output; /** * Required. The human-readable name of the flow. */ readonly displayName: pulumi.Output; /** * 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, 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 transition_routes, these handlers are evaluated on a first-match basis. The first one that matches the event get executed, with the rest being ignored. */ readonly eventHandlers: pulumi.Output; /** * The unique identifier of the flow. Format: `projects//locations//agents//flows/`. */ readonly name: pulumi.Output; /** * NLU related settings of the flow. */ readonly nluSettings: pulumi.Output; /** * 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. Transition route groups defined in the page have higher priority than those defined in the flow. Format:`projects//locations//agents//flows//transitionRouteGroups/`. */ readonly transitionRouteGroups: pulumi.Output; /** * 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 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. TransitionRoutes are evalauted in the following order: * TransitionRoutes with intent specified.. * TransitionRoutes with only condition specified. TransitionRoutes with intent specified are inherited by pages in the flow. */ readonly transitionRoutes: pulumi.Output; /** * Create a AgentFlow resource with the given unique name, arguments, and options. * * @param name The _unique_ name of the resource. * @param args The arguments to use to populate this resource's properties. * @param opts A bag of options that control this resource's behavior. */ constructor(name: string, args: AgentFlowArgs, opts?: pulumi.CustomResourceOptions); } /** * The set of arguments for constructing a AgentFlow resource. */ export interface AgentFlowArgs { readonly agentsId: pulumi.Input; /** * The description of the flow. The maximum length is 500 characters. If exceeded, the request is rejected. */ readonly description?: pulumi.Input; /** * Required. The human-readable name of the flow. */ readonly displayName?: pulumi.Input; /** * 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, 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 transition_routes, these handlers are evaluated on a first-match basis. The first one that matches the event get executed, with the rest being ignored. */ readonly eventHandlers?: pulumi.Input[]>; readonly flowsId: pulumi.Input; readonly locationsId: pulumi.Input; /** * The unique identifier of the flow. Format: `projects//locations//agents//flows/`. */ readonly name?: pulumi.Input; /** * NLU related settings of the flow. */ readonly nluSettings?: pulumi.Input; readonly projectsId: pulumi.Input; /** * 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. Transition route groups defined in the page have higher priority than those defined in the flow. Format:`projects//locations//agents//flows//transitionRouteGroups/`. */ readonly transitionRouteGroups?: pulumi.Input[]>; /** * 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 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. TransitionRoutes are evalauted in the following order: * TransitionRoutes with intent specified.. * TransitionRoutes with only condition specified. TransitionRoutes with intent specified are inherited by pages in the flow. */ readonly transitionRoutes?: pulumi.Input[]>; }