How to set dependencies on

When we started our Automation journey, a main goals of ours was to create a stable foundation for dependency connections between different pulses. Drum roll.... we're happy to present stage one, Due Date Dependencies 🙌

Dependency Column:

Have pulses with due dates that are dependent on one another? Can one pulse not start until the other is complete? That's where the dependency column comes into play. The dependency column creates vital connections between pulses that will help to better manage projects. 

How to add a dependency column

1. You can add the dependency column from our column center : 



2. Or from the dependency recipe itself:


Dependency Automation:

Now that you've added the dependency column, how do you set up the automation? To add the relevant dependency recipe to your workflow, you will first need to first visit our automation store on the top bar of your board :


There you will be able to choose from our different recipes and set up the dependency that supports your workflow : 


So let's dive into the different recipes 😀 

Dependency Recipes and Use Cases: 

1. Ensure that the {date} of a pulse always starts after the date of the {dependency}pulse:


In this use case, using the dependency column and recipe above, we've maintained our waterfall workflow and assured that no timeline will start before the other ends: 



2. Adjust the {date} of a pulse according to the change in the date of its {dependency} pulse:


This recipe will serve us when a change has happened and now we need to push out the dates of the dependent pulses. In the below example, when a timeline date is shifted out 'x' days, the pulses dependent on this date are shifted out 'x' days accordingly.



3. Ensure that the {date} of a pulse always starts after its {another date): 




For this example, we have a set of tasks under "Phase A" and we want to maintain the chronological order of our workflow. To do so, we need to make sure that the "Review status" due date will always start after the "Design status" due date. This is where the below dependency automation comes into play:


4. Adjust the {date} of a pulse according to the change in its {another date) :


On this use case, every pulse has two date columns that are dependent on each other. By using the recipe above with the addition of the second recipe (Adjust the {date} of a pulse according to the change in the date of its {dependency} pulse) we managed to set a workflow where all dates are shifting dependently and accordingly :





Note: Status related dependencies are on the horizon 🙌


If you are intrigued to learn more about our variety of automations, please check out this article- article link

And of course, if you have any further questions please don't hesitate to reach out to our customer success team right here at