> ## 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: Run Package

> Use the Run Package workflow task to execute a dataflow as a step in your Integrate.io ETL workflow and pass variable overrides.

The Run Package task executes a dataflow as a step in the current workflow.

## Overview

* Runs a dataflow as a step inside the current workflow.
* The parent workflow waits for the dataflow to finish before continuing.
* Supports overriding the dataflow's variables at run time.
* The dataflow's outcome (success or failure) decides which branch of the workflow runs next.

To run another workflow from a workflow, use the [Run Workflow task](/etl/using-components-run-workflow) instead. Run Package only accepts dataflows.

## Configuration

<Steps>
  <Step>Select the dataflow to execute.</Step>
  <Step>Optionally override the dataflow's variables with runtime values.</Step>
  <Step>Connect the task's outgoing edges to choose what runs on success, failure, or completion.</Step>
</Steps>

## Variables and secrets

The Run Package task always reads the child dataflow's current variables and secrets when it runs or is displayed in the workflow editor.

* **Variables you override on the task** are preserved. An override is any value you set on the task that the child dataflow has never had for that key.
* **Inherited variables** (values you did not change on the task) track the child dataflow. If you rename, add, remove, or change a variable on the child, the workflow reflects the change automatically.
* **Secrets** always come from the child dataflow. Per-task secret overrides are not supported. The editor shows the child's current masked secret values, and the run uses the child's real values.

You do not need to re-save the workflow when you update variables or secrets on a child dataflow. Changes are picked up on the next render or run.

### Exported workflows

When you export a workflow, each Run Package task keeps its variables as stored on the task. Inherited secrets are dropped from the export and re-inherited from the child dataflow on import.

## Use cases

* Chain multiple dataflows in sequence (for example, load staging, transform, load warehouse).
* Run a shared utility dataflow (for example, cleanup or notifications) from multiple workflows.
* Orchestrate multi-step pipelines with conditional branching based on each dataflow's outcome.