Workflows allow defining dependencies between your Models and Activations by allowing you to create a DAG (Directed Acyclic Graph) from within Hevo. You can create simple and complex queries on your Models and Activations to transform your data, and combine them either based on some data load conditions in the Destination or without any conditions. The data generated as a result of the Workflow is either loaded in the Destination, or the Target, depending on configuration of the Workflow. Read Working with Models and Working with Activate for steps to create a Model and Activation respectively.

Data load conditions

A data load condition compares the number of rows that have been loaded in a Destination table since the last run of the Workflow, with a number that you provide in the condition. Based the outcome of the Condition, for example True or False, you can define how different Models and Activations are combined in the Workflow, and whether the Workflow should stop.

You can define Conditions only on the data loaded in the Destination by Hevo.

The following example illustrates the use of Conditions in Workflows:


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.

Configure Condition

Therefore, if the number of rows in the data coming though 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.

Quantity filter condition

See Also

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-07-2022 1.97 Updated the page to reflect the latest changes intoduced in Workflows.
Last updated on 07 Sep 2022

Tell us what went wrong