Set the order your actions will run

đź•™ 2 minute read

Dependencies determine the order that tasks are executed within a Workflow instance by defining what actions need to be completed (or skipped) before a given task should be activated.

How to set a dependency

By default, when you add new actions, they will start after the previous action is completed or skipped based on the Starts after previous step is completed or skipped dependency type. This means that for the majority of actions, you won’t need to change dependencies at all.

screen readers look here

If you drag-and-drop the action to reorder it in the actions list, the dependencies for that action will automatically update.

  1. Select Workflows from the top navigation bar.
  2. Choose a Workflow, this will open the Workflow detail page.
  3. Select in the upper-right corner to get to the Workflow Builder page.
  4. Click an action to configure it, then select the drop-down in the Dependencies & Conditions section next to Starts.

    screen readers look here
  5. Select the dependency type. Select After previous step is completed or skipped to start the action after the previous action.
  6. For more complex dependencies, select When dependencies are met from the new drop-down that appears.

    screen readers look here
    1. Select the dependency type that works for you.
      • All must be completed
      • At least one must be completed
      • All must be completed or skipped
    2. Select the steps that will be evaluated. You can select multiple steps.
    3. Optionally, add or remove a dependency. Select to remove the dependency. Select Add a Dependency to add another dependency.
  7. Select .

In most cases, only one dependency type is needed. When setting up a sequence of tasks that should activate one after another, each task only needs a dependency on the prior task (not all previous tasks). In other words, in a linear process with 5 steps, step 5 is only dependent on step 4, not step 1-4. Learn more in the dependencies article.

đź’ˇTip: Review your Workflow structure carefully and only add dependencies when necessary. This will reduce any chance of bottlenecks within a Workflow instance.

Organize more complex processes with inline actions

Inline actions make it easy to work with “blocks” of actions, which are all linked together and organized in a group. You can create a conditional block with the Workflow: Start another Workflow action.

 

Blocks help organize steps, and make them more portable. A block can have it’s own dependencies and conditions: so if the dependencies are met, the entire block begins, rather than needing to configure each step within the block manually.

Learn more about conditional blocks on the Organize your processes with conditional blocks article.