Workflows

In Hevo, you can use Workflows to create a Directed Acyclic Graph (DAG). The DAG conceptually represents the Models and their order of execution. The Models may be connected by lines if data from one Model forms an input to another Model. Workflows allow you to:

• Define dependencies between SQL and dbt™ Models.

• Combine the data transformed by these Models with or without data load conditions.

• Load the transformed data to the Destination tables as per your Workflow setup.

Read Working with SQL Models and Configuring a dbt™ Project for the steps to create SQL Models and configure dbt projects, respectively.

Data load conditions

A data load condition is evaluated as either TRUE or _FALSE_ by comparing the number of rows loaded in a Destination table since the last run of the Workflow with the number defined in the condition.

Based on the outcome of the condition, you can define how different Models are combined in the Workflow, and whether the Workflow should stop.

You can define conditions only on the data loaded into the Destination tables by Hevo.

The following example illustrates the use of data load conditions:

Example

Let us consider a Model, Engineering, which is connected to Models, Employees 1 and Employees 2 through the Quantity filter condition.

Quantity filter condition: The number of rows in the Destination table _18_new_campaign is Greater than Equal To 10.

Therefore, if the number of rows in the data coming through the Engineering Model are greater than 10, it serves as input to the Employees 1 Model. Else, it serves as input to the Employees 2 Model.

---

• Articles in this section
  • Familiarizing with the Workflows UI
  • Working with Workflows
  • Viewing the Workflow History
  • Workflows FAQs
    • If I change the schedule of a Workflow, will it impact the schedule of each Model?

---

Revision History