Overview
The Workflow Editor allows you to build complex, multi-step automation pipelines by combining multiple flows into a single workflow.
In Etlworks, workflow steps are not lightweight tasks. Each step is a full flow of a specific type (for example, Database to Database, File to File, Web Service, Execute SQL, Execute Script, and others).
Every step:
- Has its own configuration
- Uses its own connections and formats
- Includes its own transformations (when applicable)
- Can be executed independently outside of a workflow
The Workflow Editor combines these flows into a structured execution model with support for unlimited nesting, conditions, loops, retries, parallel execution, and centralized failure handling.
What a Workflow Is
A workflow is an orchestration layer.
It does not replace flows.
It coordinates them.
A workflow defines:
- Which flow runs first
- Which flow runs next
- Which flow runs conditionally
- Which flow runs repeatedly
- Which flows can run in parallel
- What happens when a flow fails
The workflow itself does not contain transformations. Transformations belong to the individual steps (flows).
Steps Are Full Flows
Each step in a workflow is a full flow instance.
This means:
- You can use any supported flow type as a step
- Each step maintains its own internal logic
- Steps can include their own transformations
- Steps can be nested inside other workflows
There is no limit to nesting depth. Workflows can contain workflows, which can contain workflows.
This design keeps workflows modular and scalable.
Execution Structure
The Canvas Editor visually represents execution order.
Execution is determined by how steps are connected on the canvas.
- A step runs after its parent completes
- Execution paths are explicitly defined
- Nested workflows execute within their parent step
The visual structure reflects the actual runtime behavior.
Orchestration Capabilities
Workflows support the following orchestration capabilities:
- Conditional execution of steps
- Looping steps
- Running steps in parallel
- Implementing retry logic
- Centralized failure handling using On Exception
Each of these capabilities is configured at the workflow level and applies to steps as flows.
Detailed configuration of these features is covered in the dedicated articles in this section.
Canvas Editor
The Canvas Editor is the default Workflow Editor experience.
It provides:
- A visual representation of workflow structure
- Direct manipulation of steps
- Clear visibility into execution flow
- Simplified navigation of nested workflows
The Classic grid-based editor remains available for legacy workflows, but all new workflows should be designed and maintained using the Canvas Editor.
Summary
Workflows in Etlworks are orchestration containers for full flows.
They enable you to:
- Combine multiple flows into structured execution pipelines
- Maintain separation of logic between steps
- Scale through nesting
- Apply orchestration rules such as conditions, loops, retries, and parallel execution
The Canvas Editor provides a clear, maintainable way to design and manage these workflows.