Dependencies let you control the order in which tasks and actions are completed in a workflow. In this guide, you'll learn how to set up dependencies between workflow steps, understand how blocked tasks work, and keep your processes running in the right sequence.
For a broader overview of building workflows, see Getting Started with Workflows.
How dependencies work
A dependency is a link between two steps in a workflow — the step that must finish first (the prerequisite) and the step that is waiting (the dependent). Until the prerequisite is completed, the dependent step remains blocked and won't be actionable.
When all prerequisites for a blocked item are completed, Humaans automatically marks the dependency as satisfied and the dependent item becomes available straight away. No manual intervention is needed — the transition happens instantly.
If a task or action has multiple dependencies, it will stay blocked until all of its prerequisites have been satisfied.
Setting up dependencies
You can add dependencies when building or editing a workflow template. Here's how:
Open the workflow you want to edit and click Edit template.
Select the task or action that should wait for another step to finish.
In the configuration panel, find the Dependencies (or Starts after) section.
Choose one or more prerequisite tasks or actions from the list.
Click Publish to save your changes.
Dependencies are set at the workflow template level, so every time the workflow runs for a new employee, the same execution order is enforced automatically.
Dependency types
You can create dependencies between different types of workflow items:
Task depends on task — one task must be completed before another becomes available.
Task depends on action — an entire action (e.g. a form submission or email send) must complete before a task unblocks.
Action depends on task — a specific task must be completed before the next action can begin.
Action depends on action — one action must finish before another starts.
Parallel vs sequential execution
By default, workflow actions run in parallel — they don't wait for each other unless you explicitly set a dependency.
Parallel execution — Multiple tasks become active at the same time when the workflow starts (no dependencies set).
Sequential execution — Tasks activate one after another in a specific order (dependencies set between them).
For example, in an onboarding workflow you might want IT Setup and HR Paperwork to run in parallel (both start immediately), but Schedule first 1-on-1 should only become active after Assign onboarding buddy is complete.
Viewing blocked tasks
Blocked tasks are clearly indicated in your task list. Each blocked task displays a "Blocked by" label showing what it is waiting on. This gives you visibility into the workflow's progress without needing to check each step individually.
The blocking information shows:
The type of the blocker (task or action).
The title of the blocking item.
For more on managing tasks within workflows, see Managing workflow tasks.
Tips:
Use dependencies to enforce a logical order — for example, ensure a contract is signed before IT provisioning begins.
Keep dependency chains short where possible to avoid unnecessary delays in your workflows.
If a task seems stuck, check the "Blocked by" indicator — it will tell you exactly what needs to happen first.
Let independent tasks run in parallel to speed things up. Only add dependencies where the order truly matters.