TL;DR: Every new subitem you add automatically becomes dependent on the one created before it — building a clean dependency chain as your task list grows. Set it up once, and every new subitem joins the chain on creation. Top-15 most-used recipe in the app.
What this does
Recipe:"When subitem is created, set previous subitem as a dependency using dependency column."
The first subitem you create has no predecessor. The second one is set to depend on the first. The third depends on the second. And so on — a perfect linear chain, built automatically as you add subitems.
When to use it
Stepwise workflows where each task can only start after the previous one ends
Onboarding sequences, content production pipelines, manufacturing steps
Project plans where you want monday.com's dependency view to render a clean chain without manual setup
Combining with date-shift automations: when one subitem moves, the chain ripples
Before you start
A Dependency column on the subitem (this is monday.com's native Dependency column type)
Subitems should be added in the order you want them to execute — the recipe links each new one to the previous in the list
Set it up
Open Automate → Create on your board.
Copy the recipe text above and find it in your board's automation center, then click Use Template.
Configure: select your subitem's Dependency column.
Click Create automation.
Test that it works
On any item, create a new subitem (e.g. "Step 1"). Confirm its Dependency column is empty (it's the first).
Create a second subitem ("Step 2"). Confirm its Dependency column points to "Step 1".
Create a third subitem ("Step 3"). Confirm its Dependency column points to "Step 2".
Common gotchas
Order matters. The recipe links each new subitem to whichever subitem was created immediately before it, in order. Reordering subitems after the fact won't re-link them — dependencies stay as originally set.
The Dependency column must be the monday.com native Dependency type, not a Connect-Boards or Text column.
Existing subitems are NOT chained. This recipe fires on creation only. To bulk-link existing subitems, see the companion recipe "When item's status changes to something, set the dependency of each subitem to the subitem before it using dependency column" (one-shot bulk version).
Pair with date-shift automations. Once chained, you can use date-sync recipes so when one subitem moves, the chain ripples.
Branching workflows don't fit this pattern. The recipe builds a strict linear chain. For Y-shaped or parallel workflows, configure dependencies manually.