TL;DR: Push subitem activity into the right channels — notify owners on status changes, copy subitem updates to the parent, or trigger a status change when an update is posted. Keep teams informed without manual relay.
When to use these automations
Owners need to know when their subitems are activated or completed
Subitem-level discussion should bubble up to parent updates
An update posted on a subitem should trigger a status change automatically
Recipes
Recipe (exact text from automation center)
Use when
"When status changes to something, notify all subitems' owners."
Status flip on a parent → every subitem owner gets pinged.
"When an update is posted on a subitem, copy that update to its parent item."
Surface subitem-level discussion at the parent level — keeps reviewers in one place.
"When an update on a subitem is created, notify someone."
Direct ping to a specific person whenever a subitem update lands.
"When an update is posted on a subitem, change this status to something."
Treat any update as activity — flip the subitem to "In review" automatically.
"When a new update is posted on a subitem by someone, change this status to something."
Same as above but only fires when a specific person posts. Useful for client/handoff workflows.
"When subitem's status changes to something, post an update in the subitem with this text."
Auto-post a templated update on status changes — useful for status logs or audit trails.
"When an update is posted on a subitem, set the Date to today."
Stamp the latest activity date whenever someone posts an update — useful for tracking last-activity in dashboards.