Skip to content

flow_template.md

Latest commit

 

History

History
1064 lines (690 loc) · 37.8 KB

flow_template.md

File metadata and controls

1064 lines (690 loc) · 37.8 KB
page_title epilot-workflow_flow_template Data Source - terraform-provider-epilot-workflow
subcategory
description FlowTemplate DataSource

epilot-workflow_flow_template (Data Source)

FlowTemplate DataSource

Example Usage

data "epilot-workflow_flow_template" "my_flowtemplate" {
}

Schema

Read-Only

  • additional_triggers (Attributes List) Additional trigger configurations that can also start this flow. Useful for flows that should be startable via multiple methods (e.g., both automation AND manual). (see below for nested schema)

  • assigned_to (Attributes List) (see below for nested schema)

  • available_in_ecp (Boolean) Indicates whether this workflow is available for End Customer Portal or not. By default it's not.

  • closing_reasons (Attributes List) (see below for nested schema)

  • created_at (String) ISO String Date & Time

  • description (String)

  • due_date (String)

  • due_date_config (Attributes) Set due date for the task based on a dynamic condition (see below for nested schema)

  • edges (Attributes List) (see below for nested schema)

  • enabled (Boolean) Whether the workflow is enabled or not

  • entity_sync (Attributes List) (see below for nested schema)

  • id (String) The ID of this resource.

  • manifest (List of String) The manifest IDs associated with this workflow

  • name (String)

  • org_id (String)

  • phases (Attributes List) (see below for nested schema)

  • single_closing_reason_selection (Boolean) Whether only a single closing reason can be selected

  • tasks (Attributes List) (see below for nested schema)

  • taxonomies (List of String) Taxonomy ids that are associated with this workflow and used for filtering

  • trigger (Attributes) (see below for nested schema)

  • updated_at (String) ISO String Date & Time

  • version (String) Version of the workflow schema.

  • v1 – Deprecated. The initial version of workflows with limited structure and automation capabilities.

  • v2 – Linear workflows. Supports sequential task execution with basic automation triggers.

  • v3 – Advanced workflows. Adds support for branching logic (conditions), parallel paths, and enhanced automation features such as dynamic triggers and flow control.

Nested Schema for additional_triggers

Read-Only:

Nested Schema for additional_triggers.automation_trigger

Read-Only:

  • automation_id (String) Id of the automation config that triggers this workflow
  • id (String)
  • trigger_config (Attributes List) Transient field. Trigger configurations for creating or updating the trigger automation flow. Each item follows the automation API trigger schema. Processed by the backend during create/update and stripped before storage. (see below for nested schema)
  • type (String)

Nested Schema for additional_triggers.automation_trigger.trigger_config

Read-Only:

  • additional_properties (String) Parsed as JSON.
  • configuration (Map of String) Trigger-specific configuration
  • type (String) The trigger type (e.g. entity_operation, activity)

Nested Schema for additional_triggers.journey_automation_trigger

Read-Only:

  • entity_schema (String) Schema of the main entity where flow will be triggered. The entity will be picked from automation context.
  • id (String)
  • type (String)

Nested Schema for additional_triggers.journey_submission_trigger

Read-Only:

  • automation_id (String)
  • id (String)
  • journey_id (String) ID of the journey that will trigger this flow
  • journey_name (String) Name of the journey that will trigger this flow
  • type (String)

Nested Schema for additional_triggers.manual_trigger

Read-Only:

  • entity_schema (String)
  • id (String)
  • type (String)

Nested Schema for assigned_to

Read-Only:

  • str (String)
  • variable_assignment (Attributes) Represents a variable assignment with its expression and optional resolved value. Used for dynamic user assignments that get resolved during workflow execution. (see below for nested schema)

Nested Schema for assigned_to.variable_assignment

Read-Only:

  • value (List of String) The resolved values after variable evaluation (populated during execution)
  • variable (String) The variable expression, e.g., "{{entity.owner}}"

Nested Schema for closing_reasons

Read-Only:

  • creation_time (String)
  • id (String)
  • last_update_time (String)
  • status (String)
  • title (String)

Nested Schema for due_date_config

Read-Only:

  • duration (Number)
  • phase_id (String)
  • task_id (String)
  • type (String)
  • unit (String)

Nested Schema for edges

Read-Only:

  • condition_id (String)
  • from_id (String)
  • id (String)
  • none_met (Boolean) Indicates a default case for a decision task. Only decision task edges can have this field and the flow advances using this edge if no conditions are met.
  • to_id (String)

Nested Schema for entity_sync

Read-Only:

Nested Schema for entity_sync.target

Read-Only:

  • entity_attribute (String)
  • entity_schema (String)

Nested Schema for entity_sync.trigger

Read-Only:

  • event (String) Event or condition that triggers the entity sync. Direct triggers match EventBridge event names (PascalCase). Status triggers are deduced from event + entity status combination.
  • filter (Attributes) Optional filter to target specific tasks or phases. Specify either task_template_id OR phase_template_id (mutually exclusive). If omitted, trigger applies to all tasks/phases. (see below for nested schema)

Nested Schema for entity_sync.trigger.filter

Read-Only:

  • phase_template_id (String) Target a specific phase by its template ID (stable across executions)
  • task_template_id (String) Target a specific task by its template ID (stable across executions)

Nested Schema for entity_sync.value

Read-Only:

  • source (String)
  • value (String)

Nested Schema for phases

Read-Only:

  • assigned_to (Attributes List) (see below for nested schema)
  • due_date (String)
  • due_date_config (Attributes) Set due date for the task based on a dynamic condition (see below for nested schema)
  • id (String)
  • name (String)
  • taxonomies (List of String) Taxonomy ids that are associated with this workflow and used for filtering

Nested Schema for phases.assigned_to

Read-Only:

  • str (String)
  • variable_assignment (Attributes) Represents a variable assignment with its expression and optional resolved value. Used for dynamic user assignments that get resolved during workflow execution. (see below for nested schema)

Nested Schema for phases.assigned_to.variable_assignment

Read-Only:

  • value (List of String) The resolved values after variable evaluation (populated during execution)
  • variable (String) The variable expression, e.g., "{{entity.owner}}"

Nested Schema for phases.due_date_config

Read-Only:

  • duration (Number)
  • phase_id (String)
  • task_id (String)
  • type (String)
  • unit (String)

Nested Schema for tasks

Read-Only:

Nested Schema for tasks.ai_agent_task

Read-Only:

  • agent_config (Attributes) Configuration for AI Agent to run (see below for nested schema)
  • assigned_to (Attributes List) (see below for nested schema)
  • description (Attributes) Longer information regarding Task (see below for nested schema)
  • due_date (String)
  • due_date_config (Attributes) Set due date for the task based on a dynamic condition (see below for nested schema)
  • ecp (Attributes) Details regarding ECP for the workflow step (see below for nested schema)
  • id (String)
  • installer (Attributes) Details regarding ECP for the workflow step (see below for nested schema)
  • journey (Attributes) (see below for nested schema)
  • name (String)
  • partner (Attributes) Details regarding partner for the workflow step (see below for nested schema)
  • phase_id (String)
  • requirements (Attributes List) requirements that need to be fulfilled in order to enable the task while flow instances are running (see below for nested schema)
  • task_type (String)
  • taxonomies (List of String) Taxonomy ids that are associated with this workflow and used for filtering

Nested Schema for tasks.ai_agent_task.agent_config

Read-Only:

  • additional_properties (String) Parsed as JSON.
  • agent_id (String) Id of the configured AI Agent to run

Nested Schema for tasks.ai_agent_task.assigned_to

Read-Only:

  • str (String)
  • variable_assignment (Attributes) Represents a variable assignment with its expression and optional resolved value. Used for dynamic user assignments that get resolved during workflow execution. (see below for nested schema)

Nested Schema for tasks.ai_agent_task.assigned_to.variable_assignment

Read-Only:

  • value (List of String) The resolved values after variable evaluation (populated during execution)
  • variable (String) The variable expression, e.g., "{{entity.owner}}"

Nested Schema for tasks.ai_agent_task.description

Read-Only:

  • enabled (Boolean)
  • value (String)

Nested Schema for tasks.ai_agent_task.due_date_config

Read-Only:

  • duration (Number)
  • phase_id (String)
  • task_id (String)
  • type (String)
  • unit (String)

Nested Schema for tasks.ai_agent_task.ecp

Read-Only:

Nested Schema for tasks.ai_agent_task.ecp.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.ai_agent_task.installer

Read-Only:

Nested Schema for tasks.ai_agent_task.installer.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.ai_agent_task.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.ai_agent_task.partner

Read-Only:

  • description (String)
  • enabled (Boolean)
  • label (String)

Nested Schema for tasks.ai_agent_task.requirements

Read-Only:

  • phase_id (String) The id of the phase that it points to
  • task_id (String) The id of the task that it points to
  • when (String)

Nested Schema for tasks.automation_task

Read-Only:

  • assigned_to (Attributes List) (see below for nested schema)
  • automation_config (Attributes) Configuration for automation execution to run (see below for nested schema)
  • created_automatically (Boolean) Indicates whether this task was created automatically by journeys or manually by an user
  • description (Attributes) Longer information regarding Task (see below for nested schema)
  • due_date (String)
  • due_date_config (Attributes) Set due date for the task based on a dynamic condition (see below for nested schema)
  • ecp (Attributes) Details regarding ECP for the workflow step (see below for nested schema)
  • id (String)
  • installer (Attributes) Details regarding ECP for the workflow step (see below for nested schema)
  • journey (Attributes) (see below for nested schema)
  • name (String)
  • partner (Attributes) Details regarding partner for the workflow step (see below for nested schema)
  • phase_id (String)
  • requirements (Attributes List) requirements that need to be fulfilled in order to enable the task while flow instances are running (see below for nested schema)
  • schedule (Attributes) (see below for nested schema)
  • task_type (String)
  • taxonomies (List of String) Taxonomy ids that are associated with this workflow and used for filtering
  • trigger_mode (String)

Nested Schema for tasks.automation_task.assigned_to

Read-Only:

  • str (String)
  • variable_assignment (Attributes) Represents a variable assignment with its expression and optional resolved value. Used for dynamic user assignments that get resolved during workflow execution. (see below for nested schema)

Nested Schema for tasks.automation_task.assigned_to.variable_assignment

Read-Only:

  • value (List of String) The resolved values after variable evaluation (populated during execution)
  • variable (String) The variable expression, e.g., "{{entity.owner}}"

Nested Schema for tasks.automation_task.automation_config

Read-Only:

  • action_config (Attributes) Transient field. The full automation action configuration following the automation API action schema. Processed by the backend during create/update and stripped before storage. When present without a flow_id, a new automation flow is created. When present with a flow_id, the existing automation flow is updated. (see below for nested schema)
  • flow_id (String) Id of the configured automation to run

Nested Schema for tasks.automation_task.automation_config.action_config

Read-Only:

  • additional_properties (String) Parsed as JSON.
  • config (Map of String) Action-specific configuration
  • type (String) The action type (e.g. send-email, trigger-workflow)

Nested Schema for tasks.automation_task.description

Read-Only:

  • enabled (Boolean)
  • value (String)

Nested Schema for tasks.automation_task.due_date_config

Read-Only:

  • duration (Number)
  • phase_id (String)
  • task_id (String)
  • type (String)
  • unit (String)

Nested Schema for tasks.automation_task.ecp

Read-Only:

Nested Schema for tasks.automation_task.ecp.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.automation_task.installer

Read-Only:

Nested Schema for tasks.automation_task.installer.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.automation_task.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.automation_task.partner

Read-Only:

  • description (String)
  • enabled (Boolean)
  • label (String)

Nested Schema for tasks.automation_task.requirements

Read-Only:

  • phase_id (String) The id of the phase that it points to
  • task_id (String) The id of the task that it points to
  • when (String)

Nested Schema for tasks.automation_task.schedule

Read-Only:

Nested Schema for tasks.automation_task.schedule.delayed_schedule

Read-Only:

  • duration (Number)
  • mode (String)
  • unit (String)

Nested Schema for tasks.automation_task.schedule.immediate_schedule

Read-Only:

  • mode (String)

Nested Schema for tasks.automation_task.schedule.relative_schedule

Read-Only:

  • direction (String)
  • duration (Number)
  • mode (String)
  • reference (Attributes) (see below for nested schema)
  • unit (String)

Nested Schema for tasks.automation_task.schedule.relative_schedule.reference

Read-Only:

  • attribute (String) An entity attribute that identifies a date / datetime
  • id (String) The id of the entity / workflow / task, based on the origin of the schedule. For all_preceding_tasks_completed, use the sentinel value "all_preceding_tasks_completed".
  • origin (String)
  • schema (String) The schema of the entity

Nested Schema for tasks.decision_task

Read-Only:

Nested Schema for tasks.decision_task.assigned_to

Read-Only:

  • str (String)
  • variable_assignment (Attributes) Represents a variable assignment with its expression and optional resolved value. Used for dynamic user assignments that get resolved during workflow execution. (see below for nested schema)

Nested Schema for tasks.decision_task.assigned_to.variable_assignment

Read-Only:

  • value (List of String) The resolved values after variable evaluation (populated during execution)
  • variable (String) The variable expression, e.g., "{{entity.owner}}"

Nested Schema for tasks.decision_task.conditions

Read-Only:

  • branch_name (String) The name of the branch
  • id (String)
  • logical_operator (String)
  • statements (Attributes List) (see below for nested schema)

Nested Schema for tasks.decision_task.conditions.statements

Read-Only:

  • id (String)
  • operator (String)
  • source (Attributes) (see below for nested schema)
  • value_type (String) How to interpret values. "static" (default) means literal values. "relative_date" means values[0] is a dynamic date token like "today".
  • values (List of String)

Nested Schema for tasks.decision_task.conditions.statements.source

Read-Only:

  • attribute (String)
  • attribute_operation (String)
  • attribute_repeatable (Boolean)
  • attribute_sub_field (String) For complex attribute types, specifies which sub-field to extract (e.g., "address", "name", "email_type")
  • attribute_type (String)
  • date_offset (Attributes) Offset to apply to the source date value before comparison (e.g., +18 years for age check, +30 days for expiry) (see below for nested schema)
  • id (String) The id of the action or trigger
  • origin (String)
  • origin_type (String)
  • schema (String)

Nested Schema for tasks.decision_task.conditions.statements.source.date_offset

Read-Only:

  • amount (Number) Number of units to offset
  • unit (String) Unit of the offset

Nested Schema for tasks.decision_task.description

Read-Only:

  • enabled (Boolean)
  • value (String)

Nested Schema for tasks.decision_task.due_date_config

Read-Only:

  • duration (Number)
  • phase_id (String)
  • task_id (String)
  • type (String)
  • unit (String)

Nested Schema for tasks.decision_task.ecp

Read-Only:

Nested Schema for tasks.decision_task.ecp.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.decision_task.installer

Read-Only:

Nested Schema for tasks.decision_task.installer.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.decision_task.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.decision_task.loop_config

Read-Only:

  • exit_branch_id (String) The id of the branch that will be used to exit the loop
  • loop_branch_id (String) The id of the branch that will be looped
  • max_iterations (Number) Maximum number of iterations for the loop branch

Nested Schema for tasks.decision_task.partner

Read-Only:

  • description (String)
  • enabled (Boolean)
  • label (String)

Nested Schema for tasks.decision_task.requirements

Read-Only:

  • phase_id (String) The id of the phase that it points to
  • task_id (String) The id of the task that it points to
  • when (String)

Nested Schema for tasks.decision_task.schedule

Read-Only:

Nested Schema for tasks.decision_task.schedule.delayed_schedule

Read-Only:

  • duration (Number)
  • mode (String)
  • unit (String)

Nested Schema for tasks.decision_task.schedule.relative_schedule

Read-Only:

  • direction (String)
  • duration (Number)
  • mode (String)
  • reference (Attributes) (see below for nested schema)
  • unit (String)

Nested Schema for tasks.decision_task.schedule.relative_schedule.reference

Read-Only:

  • attribute (String) An entity attribute that identifies a date / datetime
  • id (String) The id of the entity / workflow / task, based on the origin of the schedule. For all_preceding_tasks_completed, use the sentinel value "all_preceding_tasks_completed".
  • origin (String)
  • schema (String) The schema of the entity

Nested Schema for tasks.task_base

Read-Only:

  • assigned_to (Attributes List) (see below for nested schema)
  • description (Attributes) Longer information regarding Task (see below for nested schema)
  • due_date (String)
  • due_date_config (Attributes) Set due date for the task based on a dynamic condition (see below for nested schema)
  • ecp (Attributes) Details regarding ECP for the workflow step (see below for nested schema)
  • id (String)
  • installer (Attributes) Details regarding ECP for the workflow step (see below for nested schema)
  • journey (Attributes) (see below for nested schema)
  • name (String)
  • partner (Attributes) Details regarding partner for the workflow step (see below for nested schema)
  • phase_id (String)
  • requirements (Attributes List) requirements that need to be fulfilled in order to enable the task while flow instances are running (see below for nested schema)
  • task_type (String)
  • taxonomies (List of String) Taxonomy ids that are associated with this workflow and used for filtering

Nested Schema for tasks.task_base.assigned_to

Read-Only:

  • str (String)
  • variable_assignment (Attributes) Represents a variable assignment with its expression and optional resolved value. Used for dynamic user assignments that get resolved during workflow execution. (see below for nested schema)

Nested Schema for tasks.task_base.assigned_to.variable_assignment

Read-Only:

  • value (List of String) The resolved values after variable evaluation (populated during execution)
  • variable (String) The variable expression, e.g., "{{entity.owner}}"

Nested Schema for tasks.task_base.description

Read-Only:

  • enabled (Boolean)
  • value (String)

Nested Schema for tasks.task_base.due_date_config

Read-Only:

  • duration (Number)
  • phase_id (String)
  • task_id (String)
  • type (String)
  • unit (String)

Nested Schema for tasks.task_base.ecp

Read-Only:

Nested Schema for tasks.task_base.ecp.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.task_base.installer

Read-Only:

Nested Schema for tasks.task_base.installer.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.task_base.journey

Read-Only:

  • complete_task_automatically (Boolean) If true, the task be auto completed when the journey is completed. By default it is true.
  • id (String)
  • journey_id (String)
  • name (String)

Nested Schema for tasks.task_base.partner

Read-Only:

  • description (String)
  • enabled (Boolean)
  • label (String)

Nested Schema for tasks.task_base.requirements

Read-Only:

  • phase_id (String) The id of the phase that it points to
  • task_id (String) The id of the task that it points to
  • when (String)

Nested Schema for trigger

Read-Only:

Nested Schema for trigger.automation_trigger

Read-Only:

  • automation_id (String) Id of the automation config that triggers this workflow
  • id (String)
  • trigger_config (Attributes List) Transient field. Trigger configurations for creating or updating the trigger automation flow. Each item follows the automation API trigger schema. Processed by the backend during create/update and stripped before storage. (see below for nested schema)
  • type (String)

Nested Schema for trigger.automation_trigger.trigger_config

Read-Only:

  • additional_properties (String) Parsed as JSON.
  • configuration (Map of String) Trigger-specific configuration
  • type (String) The trigger type (e.g. entity_operation, activity)

Nested Schema for trigger.journey_automation_trigger

Read-Only:

  • entity_schema (String) Schema of the main entity where flow will be triggered. The entity will be picked from automation context.
  • id (String)
  • type (String)

Nested Schema for trigger.journey_submission_trigger

Read-Only:

  • automation_id (String)
  • id (String)
  • journey_id (String) ID of the journey that will trigger this flow
  • journey_name (String) Name of the journey that will trigger this flow
  • type (String)

Nested Schema for trigger.manual_trigger

Read-Only:

  • entity_schema (String)
  • id (String)
  • type (String)