@epilot/sdk 2.12.1 → 2.13.0

package/dist/{workflow-definition.d-DOeb0KVV.d.cts → workflow-definition.d-CweGhhBU.d.cts}

@@ -4,6 +4,12 @@ import { OpenAPIClient, Parameters, UnknownParamsObject, AxiosRequestConfig, Ope
 
 
 declare namespace Components {
+    namespace Parameters {
+        export type EnforceLimitsParam = boolean;
+    }
+    export interface QueryParameters {
+        EnforceLimitsParam?: Parameters.EnforceLimitsParam;
+    }
     namespace Schemas {
         export type ActionSchedule = ImmediateSchedule | DelayedSchedule | RelativeSchedule;
         /**
@@ -178,9 +184,14 @@ declare namespace Components {
             id: string;
         }
         /**
-         * Closing reason could be not found
+         * Error response returned when a closing reason is not found.
          */
         export interface ClosingReasonNotFoundResp {
+            /**
+             * Human-readable message indicating the closing reason was not found.
+             * example:
+             * Closing reason with id 'xyz789' not found
+             */
             message?: string;
         }
         export interface ClosingReasons {
@@ -201,10 +212,28 @@ declare namespace Components {
             logical_operator: "AND" | "OR";
             statements: Statement[] | null;
         }
+        /**
+         * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+         * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+         * as blueprints that can be instantiated as flow executions.
+         *
+         */
         export interface CreateFlowTemplate {
+            /**
+             * Unique identifier for the flow template, generated by the system.
+             */
             id?: string;
+            /**
+             * Organization identifier that owns this flow template.
+             */
             org_id?: string;
+            /**
+             * Display name for the workflow, shown to users in the UI.
+             */
             name: string;
+            /**
+             * Optional detailed description of the workflow's purpose and behavior.
+             */
             description?: string;
             trigger?: /**
              * example:
@@ -295,6 +324,14 @@ declare namespace Components {
              * The manifest IDs associated with this workflow
              */
             _manifest?: string[];
+            /**
+             * When true, this is a linear flow: task enablement is computed at runtime from the graph — a task is enabled only when all of its direct predecessor tasks in its branch are done. This fully overrides any explicit per-task requirements.
+             */
+            linear?: boolean;
+            /**
+             * Non-blocking warnings for configuration limits the flow exceeds. Returned on read (get-flow) and on create/update responses. Size/count limits are soft: a flow exceeding them is still accepted and stored, and the violations are reported here so the UI can surface an informational banner. The flow is still fully editable and usable.
+             */
+            limit_warnings?: /* A configuration limit that the flow currently exceeds. Returned by the get-flow endpoint and by create/update responses so the UI can show a non-blocking banner. Size/count limit violations never cause a 400 — only structural errors do. The flow remains fully usable; users are encouraged to bring values within the limits. */ FlowLimitWarning[];
         }
         export interface DecisionTask {
             id: string;
@@ -344,9 +381,14 @@ declare namespace Components {
             };
         }
         /**
-         * Definition could be not found
+         * Error response returned when a workflow definition or flow template is not found.
          */
         export interface DefinitionNotFoundResp {
+            /**
+             * Human-readable message indicating the resource was not found.
+             * example:
+             * Definition with id 'abc123' not found
+             */
             message?: string;
         }
         export interface DelayedSchedule {
@@ -365,9 +407,16 @@ declare namespace Components {
             phase_id?: string;
         }
         /**
-         * set a Duedate for a step then a specific
+         * Configuration for calculating a due date dynamically based on workflow events.
+         * The due date is computed by adding a duration (numberOfUnits + timePeriod) to
+         * a reference point defined by actionTypeCondition (e.g., when workflow started,
+         * when a step closed, or when a phase finished).
+         *
          */
         export interface DynamicDueDate {
+            /**
+             * Number of time units to add to the reference point.
+             */
             numberOfUnits: number;
             timePeriod: TimeUnit;
             actionTypeCondition: "WORKFLOW_STARTED" | "STEP_CLOSED" | "PHASE_FINISHED";
@@ -470,7 +519,15 @@ declare namespace Components {
                 entityAttribute: string;
             };
         }
+        /**
+         * Standard error response returned when an API request fails.
+         */
         export interface ErrorResp {
+            /**
+             * Human-readable error message describing what went wrong.
+             * example:
+             * Invalid request body: name is required
+             */
             message?: string;
         }
         export interface EvaluationSource {
@@ -485,6 +542,34 @@ declare namespace Components {
             attribute_type?: "string" | "text" | "number" | "boolean" | "date" | "datetime" | "tags" | "country" | "email" | "phone" | "product" | "price" | "status" | "relation" | "multiselect" | "select" | "radio" | "relation_user" | "purpose" | "label" | "message_email_address";
             attribute_repeatable?: boolean;
             attribute_operation?: "all" | "updated" | "added" | "deleted";
+            /**
+             * Multi-attribute mode. When present and length > 1, the statement is
+             * evaluated against every listed attribute and combined via
+             * `attributes_match`. All listed attributes must share the same
+             * `attribute_type`. Mutually exclusive with `attribute_sub_field`,
+             * `date_offset`, and `attribute_operation`. When absent or length === 1,
+             * the legacy `attribute` field is used.
+             *
+             */
+            attributes?: [
+                string?,
+                string?,
+                string?,
+                string?,
+                string?,
+                string?,
+                string?,
+                string?,
+                string?,
+                string?
+            ];
+            /**
+             * Inner connector across `attributes`. `any` (default) means at least
+             * one attribute must satisfy the operator; `all` means every attribute
+             * must satisfy it. Ignored when `attributes` is absent or has length < 2.
+             *
+             */
+            attributes_match?: "any" | "all";
             /**
              * For complex attribute types, specifies which sub-field to extract (e.g., "address", "name", "email_type")
              */
@@ -503,10 +588,63 @@ declare namespace Components {
                 unit?: "days" | "months" | "years";
             };
         }
+        /**
+         * A configuration limit that the flow currently exceeds. Returned by the get-flow endpoint and by create/update responses so the UI can show a non-blocking banner. Size/count limit violations never cause a 400 — only structural errors do. The flow remains fully usable; users are encouraged to bring values within the limits.
+         */
+        export interface FlowLimitWarning {
+            /**
+             * i18n key identifying the exceeded limit (e.g. errors.task_max_incoming_edges).
+             */
+            i18nKey: string;
+            /**
+             * Human-readable description of the exceeded limit.
+             */
+            message: string;
+            /**
+             * The configured maximum for this limit.
+             */
+            max: number;
+            /**
+             * The actual value the flow currently has for this limit (e.g. the actual number of incoming connections).
+             */
+            current?: number;
+            /**
+             * ID of the task/node the limit applies to, when applicable.
+             */
+            node_id?: string;
+            task_name?: string;
+            branch_name?: string;
+            /**
+             * Name of the AI-agent parameter the limit applies to, when applicable.
+             */
+            param_name?: string;
+            /**
+             * JSON path within the flow to the offending value.
+             */
+            path: any[];
+        }
+        /**
+         * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+         * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+         * as blueprints that can be instantiated as flow executions.
+         *
+         */
         export interface FlowTemplate {
+            /**
+             * Unique identifier for the flow template, generated by the system.
+             */
             id?: string;
+            /**
+             * Organization identifier that owns this flow template.
+             */
             org_id?: string;
+            /**
+             * Display name for the workflow, shown to users in the UI.
+             */
             name: string;
+            /**
+             * Optional detailed description of the workflow's purpose and behavior.
+             */
             description?: string;
             trigger?: /**
              * example:
@@ -597,11 +735,37 @@ declare namespace Components {
              * The manifest IDs associated with this workflow
              */
             _manifest?: string[];
+            /**
+             * When true, this is a linear flow: task enablement is computed at runtime from the graph — a task is enabled only when all of its direct predecessor tasks in its branch are done. This fully overrides any explicit per-task requirements.
+             */
+            linear?: boolean;
+            /**
+             * Non-blocking warnings for configuration limits the flow exceeds. Returned on read (get-flow) and on create/update responses. Size/count limits are soft: a flow exceeding them is still accepted and stored, and the violations are reported here so the UI can surface an informational banner. The flow is still fully editable and usable.
+             */
+            limit_warnings?: /* A configuration limit that the flow currently exceeds. Returned by the get-flow endpoint and by create/update responses so the UI can show a non-blocking banner. Size/count limit violations never cause a 400 — only structural errors do. The flow remains fully usable; users are encouraged to bring values within the limits. */ FlowLimitWarning[];
         }
+        /**
+         * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+         * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+         * as blueprints that can be instantiated as flow executions.
+         *
+         */
         export interface FlowTemplateBase {
+            /**
+             * Unique identifier for the flow template, generated by the system.
+             */
             id?: string;
+            /**
+             * Organization identifier that owns this flow template.
+             */
             org_id?: string;
+            /**
+             * Display name for the workflow, shown to users in the UI.
+             */
             name: string;
+            /**
+             * Optional detailed description of the workflow's purpose and behavior.
+             */
             description?: string;
             trigger?: /**
              * example:
@@ -692,6 +856,14 @@ declare namespace Components {
              * The manifest IDs associated with this workflow
              */
             _manifest?: string[];
+            /**
+             * When true, this is a linear flow: task enablement is computed at runtime from the graph — a task is enabled only when all of its direct predecessor tasks in its branch are done. This fully overrides any explicit per-task requirements.
+             */
+            linear?: boolean;
+            /**
+             * Non-blocking warnings for configuration limits the flow exceeds. Returned on read (get-flow) and on create/update responses. Size/count limits are soft: a flow exceeding them is still accepted and stored, and the violations are reported here so the UI can surface an informational banner. The flow is still fully editable and usable.
+             */
+            limit_warnings?: /* A configuration limit that the flow currently exceeds. Returned by the get-flow endpoint and by create/update responses so the UI can show a non-blocking banner. Size/count limit violations never cause a 400 — only structural errors do. The flow remains fully usable; users are encouraged to bring values within the limits. */ FlowLimitWarning[];
         }
         /**
          * Short unique id (length 8) to identify the Flow Template.
@@ -700,7 +872,13 @@ declare namespace Components {
          */
         export type FlowTemplateId = string;
         export interface FlowTemplatesList {
-            results: FlowTemplate[];
+            results: /**
+             * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+             * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+             * as blueprints that can be instantiated as flow executions.
+             *
+             */
+            FlowTemplate[];
         }
         export interface ImmediateSchedule {
             mode?: "immediate";
@@ -830,7 +1008,14 @@ declare namespace Components {
              * 2021-04-27T12:00:00.000Z
              */
             dueDate?: string;
-            dynamicDueDate?: /* set a Duedate for a step then a specific */ DynamicDueDate;
+            dynamicDueDate?: /**
+             * Configuration for calculating a due date dynamically based on workflow events.
+             * The due date is computed by adding a duration (numberOfUnits + timePeriod) to
+             * a reference point defined by actionTypeCondition (e.g., when workflow started,
+             * when a step closed, or when a phase finished).
+             *
+             */
+            DynamicDueDate;
             assignedTo?: string[];
             steps: /* Action that needs to be done in a Workflow */ Step[];
             /**
@@ -869,7 +1054,14 @@ declare namespace Components {
              * 2021-04-27T12:00:00.000Z
              */
             dueDate?: string;
-            dynamicDueDate?: /* set a Duedate for a step then a specific */ DynamicDueDate;
+            dynamicDueDate?: /**
+             * Configuration for calculating a due date dynamically based on workflow events.
+             * The due date is computed by adding a duration (numberOfUnits + timePeriod) to
+             * a reference point defined by actionTypeCondition (e.g., when workflow started,
+             * when a step closed, or when a phase finished).
+             *
+             */
+            DynamicDueDate;
             /**
              * This field is deprecated. Please use assignedTo
              */
@@ -947,7 +1139,7 @@ declare namespace Components {
             task_type: TaskType;
         }
         export type TaskType = "MANUAL" | "AUTOMATION" | "DECISION" | "AI_AGENT";
-        export type TimeUnit = "minutes" | "hours" | "days" | "weeks" | "months";
+        export type TimeUnit = "minutes" | "hours" | "days" | "weeks" | "months" | "years";
         /**
          * example:
          * {
@@ -1010,9 +1202,25 @@ declare namespace Components {
          * 2
          */
         export type Version = "v1" | "v2" | "v3";
+        /**
+         * V1 workflow definition schema. Defines a linear workflow structure with sections
+         * and steps. Sections group related steps together, and steps represent individual
+         * tasks that need to be completed. This is the legacy workflow model; for new
+         * implementations, consider using V2 flow templates instead.
+         *
+         */
         export interface WorkflowDefinition {
+            /**
+             * Unique identifier for the workflow definition, generated by the system.
+             */
             id?: string;
+            /**
+             * Display name for the workflow, shown to users in the UI.
+             */
             name: string;
+            /**
+             * Optional detailed description of the workflow's purpose and behavior.
+             */
             description?: string;
             /**
              * ISO String Date & Time
@@ -1035,7 +1243,14 @@ declare namespace Components {
              * 2021-04-27T12:00:00.000Z
              */
             dueDate?: string;
-            dynamicDueDate?: /* set a Duedate for a step then a specific */ DynamicDueDate;
+            dynamicDueDate?: /**
+             * Configuration for calculating a due date dynamically based on workflow events.
+             * The due date is computed by adding a duration (numberOfUnits + timePeriod) to
+             * a reference point defined by actionTypeCondition (e.g., when workflow started,
+             * when a step closed, or when a phase finished).
+             *
+             */
+            DynamicDueDate;
             /**
              * This field is deprecated. Please use assignedTo
              */
@@ -1075,8 +1290,8 @@ declare namespace Paths {
         namespace Responses {
             export interface $202 {
             }
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace CreateClosingReason {
@@ -1086,21 +1301,53 @@ declare namespace Paths {
         }
     }
     namespace CreateDefinition {
-        export type RequestBody = Components.Schemas.WorkflowDefinition;
+        export type RequestBody = /**
+         * V1 workflow definition schema. Defines a linear workflow structure with sections
+         * and steps. Sections group related steps together, and steps represent individual
+         * tasks that need to be completed. This is the legacy workflow model; for new
+         * implementations, consider using V2 flow templates instead.
+         *
+         */
+        Components.Schemas.WorkflowDefinition;
         namespace Responses {
-            export type $201 = Components.Schemas.WorkflowDefinition;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $201 = /**
+             * V1 workflow definition schema. Defines a linear workflow structure with sections
+             * and steps. Sections group related steps together, and steps represent individual
+             * tasks that need to be completed. This is the legacy workflow model; for new
+             * implementations, consider using V2 flow templates instead.
+             *
+             */
+            Components.Schemas.WorkflowDefinition;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace CreateFlowTemplate {
-        export type RequestBody = Components.Schemas.CreateFlowTemplate;
+        namespace Parameters {
+            export type EnforceLimits = boolean;
+        }
+        export interface QueryParameters {
+            enforce_limits?: Parameters.EnforceLimits;
+        }
+        export type RequestBody = /**
+         * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+         * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+         * as blueprints that can be instantiated as flow executions.
+         *
+         */
+        Components.Schemas.CreateFlowTemplate;
         namespace Responses {
-            export type $201 = Components.Schemas.FlowTemplate;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $201 = /**
+             * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+             * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+             * as blueprints that can be instantiated as flow executions.
+             *
+             */
+            Components.Schemas.FlowTemplate;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace DeleteClosingReason {
@@ -1121,8 +1368,8 @@ declare namespace Paths {
         namespace Responses {
             export interface $204 {
             }
-            export type $403 = Components.Schemas.ErrorResp;
-            export type $404 = /* Closing reason could be not found */ Components.Schemas.ClosingReasonNotFoundResp;
+            export type $403 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a closing reason is not found. */ Components.Schemas.ClosingReasonNotFoundResp;
         }
     }
     namespace DeleteDefinition {
@@ -1135,7 +1382,7 @@ declare namespace Paths {
         namespace Responses {
             export interface $204 {
             }
-            export type $401 = Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
             export interface $404 {
             }
         }
@@ -1155,9 +1402,9 @@ declare namespace Paths {
         namespace Responses {
             export interface $204 {
             }
-            export type $401 = Components.Schemas.ErrorResp;
-            export interface $404 {
-            }
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a workflow definition or flow template is not found. */ Components.Schemas.DefinitionNotFoundResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace DuplicateFlowTemplate {
@@ -1173,10 +1420,17 @@ declare namespace Paths {
             flowId: Parameters.FlowId;
         }
         namespace Responses {
-            export type $201 = Components.Schemas.FlowTemplate;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $201 = /**
+             * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+             * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+             * as blueprints that can be instantiated as flow executions.
+             *
+             */
+            Components.Schemas.FlowTemplate;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a workflow definition or flow template is not found. */ Components.Schemas.DefinitionNotFoundResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace GetAllClosingReasons {
@@ -1207,9 +1461,9 @@ declare namespace Paths {
         }
         namespace Responses {
             export type $200 = /* One Closing reason for a workflow */ Components.Schemas.ClosingReason;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $403 = Components.Schemas.ErrorResp;
-            export type $404 = /* Closing reason could be not found */ Components.Schemas.ClosingReasonNotFoundResp;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $403 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a closing reason is not found. */ Components.Schemas.ClosingReasonNotFoundResp;
         }
     }
     namespace GetClosingReasonV1 {
@@ -1221,10 +1475,10 @@ declare namespace Paths {
         }
         namespace Responses {
             export type $200 = /* One Closing reason for a workflow */ Components.Schemas.ClosingReason;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $404 = /* Closing reason could be not found */ Components.Schemas.ClosingReasonNotFoundResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a closing reason is not found. */ Components.Schemas.ClosingReasonNotFoundResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace GetDefinition {
@@ -1235,17 +1489,31 @@ declare namespace Paths {
             definitionId: Parameters.DefinitionId;
         }
         namespace Responses {
-            export type $200 = Components.Schemas.WorkflowDefinition;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $404 = /* Definition could be not found */ Components.Schemas.DefinitionNotFoundResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $200 = /**
+             * V1 workflow definition schema. Defines a linear workflow structure with sections
+             * and steps. Sections group related steps together, and steps represent individual
+             * tasks that need to be completed. This is the legacy workflow model; for new
+             * implementations, consider using V2 flow templates instead.
+             *
+             */
+            Components.Schemas.WorkflowDefinition;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a workflow definition or flow template is not found. */ Components.Schemas.DefinitionNotFoundResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace GetDefinitions {
         namespace Responses {
-            export type $200 = Components.Schemas.WorkflowDefinition[];
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $200 = /**
+             * V1 workflow definition schema. Defines a linear workflow structure with sections
+             * and steps. Sections group related steps together, and steps represent individual
+             * tasks that need to be completed. This is the legacy workflow model; for new
+             * implementations, consider using V2 flow templates instead.
+             *
+             */
+            Components.Schemas.WorkflowDefinition[];
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace GetFlowTemplate {
@@ -1261,17 +1529,23 @@ declare namespace Paths {
             flowId: Parameters.FlowId;
         }
         namespace Responses {
-            export type $200 = Components.Schemas.FlowTemplate;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $404 = /* Definition could be not found */ Components.Schemas.DefinitionNotFoundResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $200 = /**
+             * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+             * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+             * as blueprints that can be instantiated as flow executions.
+             *
+             */
+            Components.Schemas.FlowTemplate;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a workflow definition or flow template is not found. */ Components.Schemas.DefinitionNotFoundResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace GetMaxAllowedLimit {
         namespace Responses {
             export type $200 = Components.Schemas.MaxAllowedLimit;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace GetWorkflowClosingReasons {
@@ -1298,7 +1572,7 @@ declare namespace Paths {
         }
         namespace Responses {
             export type $200 = Components.Schemas.FlowTemplatesList;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace SearchFlowTemplates {
@@ -1306,9 +1580,15 @@ declare namespace Paths {
         namespace Responses {
             export interface $200 {
                 hits?: number;
-                results?: Components.Schemas.FlowTemplate[];
+                results?: /**
+                 * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+                 * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+                 * as blueprints that can be instantiated as flow executions.
+                 *
+                 */
+                Components.Schemas.FlowTemplate[];
             }
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace SetWorkflowClosingReasons {
@@ -1342,9 +1622,9 @@ declare namespace Paths {
         export type RequestBody = /* One Closing reason for a workflow */ Components.Schemas.ClosingReason;
         namespace Responses {
             export type $200 = /* One Closing reason for a workflow */ Components.Schemas.ClosingReason;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $403 = Components.Schemas.ErrorResp;
-            export type $404 = /* Closing reason could be not found */ Components.Schemas.ClosingReasonNotFoundResp;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $403 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a closing reason is not found. */ Components.Schemas.ClosingReasonNotFoundResp;
         }
     }
     namespace UpdateDefinition {
@@ -1354,16 +1634,31 @@ declare namespace Paths {
         export interface PathParameters {
             definitionId: Parameters.DefinitionId;
         }
-        export type RequestBody = Components.Schemas.WorkflowDefinition;
+        export type RequestBody = /**
+         * V1 workflow definition schema. Defines a linear workflow structure with sections
+         * and steps. Sections group related steps together, and steps represent individual
+         * tasks that need to be completed. This is the legacy workflow model; for new
+         * implementations, consider using V2 flow templates instead.
+         *
+         */
+        Components.Schemas.WorkflowDefinition;
         namespace Responses {
-            export type $200 = Components.Schemas.WorkflowDefinition;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $200 = /**
+             * V1 workflow definition schema. Defines a linear workflow structure with sections
+             * and steps. Sections group related steps together, and steps represent individual
+             * tasks that need to be completed. This is the legacy workflow model; for new
+             * implementations, consider using V2 flow templates instead.
+             *
+             */
+            Components.Schemas.WorkflowDefinition;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
     namespace UpdateFlowTemplate {
         namespace Parameters {
+            export type EnforceLimits = boolean;
             export type FlowId = /**
              * Short unique id (length 8) to identify the Flow Template.
              * example:
@@ -1374,13 +1669,29 @@ declare namespace Paths {
         export interface PathParameters {
             flowId: Parameters.FlowId;
         }
-        export type RequestBody = Components.Schemas.FlowTemplate;
+        export interface QueryParameters {
+            enforce_limits?: Parameters.EnforceLimits;
+        }
+        export type RequestBody = /**
+         * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+         * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+         * as blueprints that can be instantiated as flow executions.
+         *
+         */
+        Components.Schemas.FlowTemplate;
         namespace Responses {
-            export type $200 = Components.Schemas.FlowTemplate;
-            export type $400 = Components.Schemas.ErrorResp;
-            export type $401 = Components.Schemas.ErrorResp;
-            export type $409 = Components.Schemas.ErrorResp;
-            export type $500 = Components.Schemas.ErrorResp;
+            export type $200 = /**
+             * Base schema for V2 flow templates. A flow template defines the structure of a workflow
+             * including phases, tasks, edges, triggers, and other configuration. Flow templates serve
+             * as blueprints that can be instantiated as flow executions.
+             *
+             */
+            Components.Schemas.FlowTemplate;
+            export type $400 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $401 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $404 = /* Error response returned when a workflow definition or flow template is not found. */ Components.Schemas.DefinitionNotFoundResp;
+            export type $409 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
+            export type $500 = /* Standard error response returned when an API request fails. */ Components.Schemas.ErrorResp;
         }
     }
 }
@@ -1400,7 +1711,7 @@ interface OperationMethods {
   /**
    * getDefinitions - getDefinitions
    * 
-   * Retrieve all Workflow Definitions from an Organization
+   * Retrieve all V1 workflow definitions belonging to the authenticated organization.
    */
   'getDefinitions'(
     parameters?: Parameters<UnknownParamsObject> | null,
@@ -1410,7 +1721,10 @@ interface OperationMethods {
   /**
    * createDefinition - createDefinition
    * 
-   * Create a Workflow Definition.
+   * Create a new V1 workflow definition. The definition consists of sections and steps
+   * that define the structure of the workflow. Once created, the definition can be used
+   * to start workflow executions.
+   * 
    */
   'createDefinition'(
     parameters?: Parameters<UnknownParamsObject> | null,
@@ -1430,10 +1744,15 @@ interface OperationMethods {
   /**
    * createFlowTemplate - createFlowTemplate
    * 
-   * Create a new Flow Template.
+   * Create a new Flow Template (V2 workflow definition).
+   * 
+   * A flow template defines the structure of a workflow including its phases, tasks,
+   * edges (connections between tasks), and trigger configuration. Once created, the
+   * template can be used to start workflow executions.
+   * 
    */
   'createFlowTemplate'(
-    parameters?: Parameters<UnknownParamsObject> | null,
+    parameters?: Parameters<Paths.CreateFlowTemplate.QueryParameters> | null,
     data?: Paths.CreateFlowTemplate.RequestBody,
     config?: AxiosRequestConfig  
   ): OperationResponse<Paths.CreateFlowTemplate.Responses.$201>
@@ -1450,7 +1769,7 @@ interface OperationMethods {
   /**
    * getFlowTemplate - getFlowTemplate
    * 
-   * Get specific FLow template for a customer
+   * Retrieve a specific flow template by its unique identifier.
    */
   'getFlowTemplate'(
     parameters?: Parameters<Paths.GetFlowTemplate.PathParameters> | null,
@@ -1463,7 +1782,7 @@ interface OperationMethods {
    * Update Flow Template.
    */
   'updateFlowTemplate'(
-    parameters?: Parameters<Paths.UpdateFlowTemplate.PathParameters> | null,
+    parameters?: Parameters<Paths.UpdateFlowTemplate.QueryParameters & Paths.UpdateFlowTemplate.PathParameters> | null,
     data?: Paths.UpdateFlowTemplate.RequestBody,
     config?: AxiosRequestConfig  
   ): OperationResponse<Paths.UpdateFlowTemplate.Responses.$200>
@@ -1480,7 +1799,10 @@ interface OperationMethods {
   /**
    * duplicateFlowTemplate - duplicateFlowTemplate
    * 
-   * Duplicate a Flow Template from an existing workflow.
+   * Create a copy of an existing flow template. The duplicated template will have a new
+   * unique identifier and can be modified independently of the original. This is useful
+   * for creating variations of existing workflows without starting from scratch.
+   * 
    */
   'duplicateFlowTemplate'(
     parameters?: Parameters<Paths.DuplicateFlowTemplate.PathParameters> | null,
@@ -1626,7 +1948,7 @@ interface PathsDictionary {
     /**
      * getDefinitions - getDefinitions
      * 
-     * Retrieve all Workflow Definitions from an Organization
+     * Retrieve all V1 workflow definitions belonging to the authenticated organization.
      */
     'get'(
       parameters?: Parameters<UnknownParamsObject> | null,
@@ -1636,7 +1958,10 @@ interface PathsDictionary {
     /**
      * createDefinition - createDefinition
      * 
-     * Create a Workflow Definition.
+     * Create a new V1 workflow definition. The definition consists of sections and steps
+     * that define the structure of the workflow. Once created, the definition can be used
+     * to start workflow executions.
+     * 
      */
     'post'(
       parameters?: Parameters<UnknownParamsObject> | null,
@@ -1658,10 +1983,15 @@ interface PathsDictionary {
     /**
      * createFlowTemplate - createFlowTemplate
      * 
-     * Create a new Flow Template.
+     * Create a new Flow Template (V2 workflow definition).
+     * 
+     * A flow template defines the structure of a workflow including its phases, tasks,
+     * edges (connections between tasks), and trigger configuration. Once created, the
+     * template can be used to start workflow executions.
+     * 
      */
     'post'(
-      parameters?: Parameters<UnknownParamsObject> | null,
+      parameters?: Parameters<Paths.CreateFlowTemplate.QueryParameters> | null,
       data?: Paths.CreateFlowTemplate.RequestBody,
       config?: AxiosRequestConfig  
     ): OperationResponse<Paths.CreateFlowTemplate.Responses.$201>
@@ -1682,7 +2012,7 @@ interface PathsDictionary {
     /**
      * getFlowTemplate - getFlowTemplate
      * 
-     * Get specific FLow template for a customer
+     * Retrieve a specific flow template by its unique identifier.
      */
     'get'(
       parameters?: Parameters<Paths.GetFlowTemplate.PathParameters> | null,
@@ -1695,7 +2025,7 @@ interface PathsDictionary {
      * Update Flow Template.
      */
     'put'(
-      parameters?: Parameters<Paths.UpdateFlowTemplate.PathParameters> | null,
+      parameters?: Parameters<Paths.UpdateFlowTemplate.QueryParameters & Paths.UpdateFlowTemplate.PathParameters> | null,
       data?: Paths.UpdateFlowTemplate.RequestBody,
       config?: AxiosRequestConfig  
     ): OperationResponse<Paths.UpdateFlowTemplate.Responses.$200>
@@ -1714,7 +2044,10 @@ interface PathsDictionary {
     /**
      * duplicateFlowTemplate - duplicateFlowTemplate
      * 
-     * Duplicate a Flow Template from an existing workflow.
+     * Create a copy of an existing flow template. The duplicated template will have a new
+     * unique identifier and can be modified independently of the original. This is useful
+     * for creating variations of existing workflows without starting from scratch.
+     * 
      */
     'post'(
       parameters?: Parameters<Paths.DuplicateFlowTemplate.PathParameters> | null,
@@ -1884,6 +2217,7 @@ type EnableRequirement = Components.Schemas.EnableRequirement;
 type EntitySync = Components.Schemas.EntitySync;
 type ErrorResp = Components.Schemas.ErrorResp;
 type EvaluationSource = Components.Schemas.EvaluationSource;
+type FlowLimitWarning = Components.Schemas.FlowLimitWarning;
 type FlowTemplate = Components.Schemas.FlowTemplate;
 type FlowTemplateBase = Components.Schemas.FlowTemplateBase;
 type FlowTemplateId = Components.Schemas.FlowTemplateId;
@@ -1919,4 +2253,4 @@ type VariableAssignment = Components.Schemas.VariableAssignment;
 type Version = Components.Schemas.Version;
 type WorkflowDefinition = Components.Schemas.WorkflowDefinition;
 
-export { type StepRequirement as $, type ActionSchedule as A, type FlowTemplateBase as B, type Client as C, type DecisionTask as D, type ECPDetails as E, type FlowTemplate as F, type FlowTemplateId as G, type FlowTemplatesList as H, type ImmediateSchedule as I, type ItemType as J, type JourneyAutomationTrigger as K, type JourneySubmissionTrigger as L, type ManualTask as M, type ManualTrigger as N, type OperationMethods as O, Paths as P, type MaxAllowedLimit as Q, type Operator as R, type PartnerDetails as S, type Phase as T, type RelativeSchedule as U, SearchFlowTemplates as V, type Section as W, type Statement as X, type Step as Y, type StepDescription as Z, type StepJourney as _, Components as a, type StepType as a0, type Task as a1, type TaskBase as a2, type TaskType as a3, type TimeUnit as a4, type Trigger as a5, type TriggerMode as a6, type TriggerType as a7, type UpdateEntityAttributes as a8, type VariableAssignment as a9, type Version as aa, type WorkflowDefinition as ab, type PathsDictionary as b, type AgentConfig as c, type AiAgentTask as d, type AutomationConfig as e, type AutomationInputContext as f, type AutomationTask as g, type AutomationTrigger as h, type ChangeReasonStatusReq as i, type ClosingReason as j, type ClosingReasonId as k, type ClosingReasonNotFoundResp as l, type ClosingReasons as m, type ClosingReasonsIds as n, type ClosingReasonsStatus as o, type Condition as p, CreateFlowTemplate as q, type DefinitionNotFoundResp as r, type DelayedSchedule as s, type DueDateConfig as t, type DynamicDueDate as u, type Edge as v, type EnableRequirement as w, type EntitySync as x, type ErrorResp as y, type EvaluationSource as z };
+export { type StepJourney as $, type ActionSchedule as A, type FlowTemplate as B, type Client as C, type DecisionTask as D, type ECPDetails as E, type FlowLimitWarning as F, type FlowTemplateBase as G, type FlowTemplateId as H, type FlowTemplatesList as I, type ImmediateSchedule as J, type ItemType as K, type JourneyAutomationTrigger as L, type JourneySubmissionTrigger as M, type ManualTask as N, type OperationMethods as O, Paths as P, type ManualTrigger as Q, type MaxAllowedLimit as R, type Operator as S, type PartnerDetails as T, type Phase as U, type RelativeSchedule as V, SearchFlowTemplates as W, type Section as X, type Statement as Y, type Step as Z, type StepDescription as _, Components as a, type StepRequirement as a0, type StepType as a1, type Task as a2, type TaskBase as a3, type TaskType as a4, type TimeUnit as a5, type Trigger as a6, type TriggerMode as a7, type TriggerType as a8, type UpdateEntityAttributes as a9, type VariableAssignment as aa, type Version as ab, type WorkflowDefinition as ac, type PathsDictionary as b, type AgentConfig as c, type AiAgentTask as d, type AutomationConfig as e, type AutomationInputContext as f, type AutomationTask as g, type AutomationTrigger as h, type ChangeReasonStatusReq as i, type ClosingReason as j, type ClosingReasonId as k, type ClosingReasonNotFoundResp as l, type ClosingReasons as m, type ClosingReasonsIds as n, type ClosingReasonsStatus as o, type Condition as p, CreateFlowTemplate as q, type DefinitionNotFoundResp as r, type DelayedSchedule as s, type DueDateConfig as t, type DynamicDueDate as u, type Edge as v, type EnableRequirement as w, type EntitySync as x, type ErrorResp as y, type EvaluationSource as z };