Workflows

Workflows allow defining dependencies between your SQL Models, dbt Models, and Activations by allowing you to create a Directed Acyclic Graph (DAG) from within Hevo. You can combine the data transformed by your Models and the data fetched by your Activation query based on the configured data load conditions, or without any conditions. The data generated by a Workflow is either loaded into the Destination tables or synchronized with the Activation Target object, depending on the configuration of the Workflow. Read Working with SQL Models, Configuring a dbt™ Project, and Creating an Activation for the steps to create SQL Models, configure dbt projects, and create Activations, respectively.

Data load conditions

A data load condition is evaluated to be 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 the different Models and Activations 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 conditions in Workflows:

Example

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

The condition Quantity filter states that 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.

---

Revision History

• 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?