> ## Documentation Index
> Fetch the complete documentation index at: https://www.integrate.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# ETL: Creating a Workflow
> Create workflow packages in Integrate.io ETL to orchestrate multi-step tasks. Define sequential and conditional task execution with error handling.
## To create a workflow:
On the main menu, click **Packages**.
Click **New package**.
Optionally, set a name and/or description
Select **workflow** option from Type dropdown
Click **Create package** to create workflow package.
Click **+ Add Task** button.
Choose task.
Add additional tasks as required
Connect tasks to create sequence of task execution. Click the connect icon on the dotted line to set the execution condition:
* **On success (default)** - task will be executed once the preceding task was executed successfully
* **On failure** - task will be executed once the preceding task execution failed
* **On completion** - task will be executed once the preceding task completed, regardless to the completion status (failed/succeeded)
## Execute SQL task
Select your DB connection.
Write the SQL query that should be executed, and select the query result type from **Result type** dropdown. You can test the query by clicking **Test Query**.
You can assign the return value to a workflow variable.
If there are at least two preceding tasks, choose task execution condition:
* all preceding conditions evaluate to true (AND)
* one of the preceding conditions evaluate to true (OR)
**Note**:
BigQuery connections uses standard SQL within Execute SQL task
## Run package task
Select the package to run
Optionally, you may edit the dataflow variables if you want to override the values with workflow variables.
If there are at least two preceding tasks, choose task execution condition:
* all preceding conditions evaluate to true (AND)
* one of the preceding conditions evaluate to true (OR)
## File mover task
Select a file storage connection as the source of the file(s)
Input source bucket (if connection requires a bucket) as well as the source path
You can enable following options on the source connection:
* Delete files from source
* Fail if the source is empty
Select a file storage connection as the destination of the file(s)
Input destination bucket (if connection requires a bucket) as well as the destination path. Any directories/folders in the path must already exist. If you wish to change the name of the file, define the path all the way to the file name and extension - for example, directory\_name/new\_file\_name.csv
If there are at least two preceding tasks, choose task execution condition:
* all preceding conditions evaluate to true (AND)
* one of the preceding conditions evaluate to true (OR)
**Note**:
Package variable (\`\$\`) and Wildcard file pattern (\`\*\`) can be applied as bucket or path name.
## Using Variables in Workflows
User variables can be defined at the workflow package level and can be used for both the Execute SQL Task and the Run Package Task.
1. **Execute SQL Task**
* Variables can also be assigned values by the Execute SQL task. This is useful if you want to have dynamic values on your variable and use it later on.
* When using variables in a SQL query, enclose the variable within curly brackets (i.e: `'${var\_name}'`).
* Example of using a variable within the Execute SQL task query:\
DELETE FROM event\
WHERE `date>='${START\_DATE}'`\
AND `date<='${END\_DATE}'`
2. **Run Package Task**
* Workflow package level variables can be used to override dataflow level variables. Here's an example:
**Note:**
Take note that we address package variables regularly as **\$variable\_name** which is different from the way we used it on Execute SQL Task above.
* If both workflow and dataflow variables have the same name, you will still have to assign the workflow variable to the dataflow variable.
* If a task dataflow uses a variable that isn't defined at the dataflow level but is assigned a value at the workflow level, the dataflow task will use the workflow variable value.