# Orchestration Integrations


RudderStack's orchestration integrations let you manage [Profiles]({{< ref "profiles/overview/_index.md" >}}) and [Reverse ETL]({{< ref "data-pipelines/reverse-etl/" >}}) jobs in your orchestration platform.

{{< info >}}
RudderStack supports [Apache Airflow]({{< ref "orchestration/airflow.md" >}}) and [Dagster]({{< ref "orchestration/dagster.md" >}}) currently.
{{< /info >}}

## Use cases

You can use the orchestration integrations to orchestrate your Profiles jobs, Reverse ETL syncs, or both.

| Use case | Description |  Example |
| :------| :------| :------|
| **Profiles jobs** | Trigger a Profiles project run when a dependent ETL or other load job completes successfully. | When an `ORDERS` table loads, you want to run your Profiles project so that your `customer_lifetime_value` and `total_orders` features are updated in the customer 360 table. |
| **Reverse ETL jobs** | Trigger a Reverse ETL sync when a transformation job runs successfully. | When a dbt model runs successfully, you can sync the output to a business tool automatically. |
| **Profiles and Reverse ETL jobs** | Trigger a Reverse ETL sync when a Profiles job runs successfully. | You want to automatically update marketing and sales tools with the latest known user information from Profiles. |

<br />