Sync column values from parent items to subitems

Introduction

Using the Subitem Automations app for  Monday.com , you can automatically sync values from a parent item down to its subitems. This includes Status, People, Date, Dropdown, Text, Numbers, and most other column types (excluding Read-only columns).
These automations help reduce manual work, prevent mistakes, and ensure subitems always stay aligned with their parent item.
This article walks through all available automation recipes that sync parent item values to subitems, explains when each one should be used, and provides real-world examples so you can choose the best option for your setup.

What it does

These automations automatically copy values from a parent item to its subitems based on different triggers and conditions, such as:
  • When a subitem is created
  • When a parent item’s column changes
  • When a subitem meets a specific condition (status, name, empty column, etc.)
Each recipe produces a similar outcome (syncing values) but is designed for different workflows and timing requirements.

When to use this

Use these automations if you want to:
  • Ensure subitems inherit key details from the parent item
  • Keep subitems in sync when parent item values change
  • Avoid manually updating multiple subitems
  • Control when and which subitems receive updates

Available automation recipes

Below is a breakdown of each automation recipe, exactly as it appears in  Monday.com , along with recommended use cases.


Sync values when a subitem is created

Automation recipe:
“When subitem is created, set value of its column to match the value of column in parent item”
What it doesCopies a column value from the parent item to the subitem at the moment the subitem is created.
Best use caseUse this when you want every new subitem to automatically inherit a value from the parent item, but you don’t want existing subitems to change later.
Example
  • Parent item has an Owner (People column)
  • Every new subitem should automatically get the same owner
  • Existing subitems should remain untouched if the owner later changes


Sync values when a parent item column changes

Automation recipe:
“When column changes on an item, change its subitems’ column to the same value”
What it doesUpdates the selected column on all existing subitems whenever the parent item’s column changes.
Best use caseUse this when subitems must always stay in sync with the parent item, even after creation.
Example
  • Parent item Status changes from Working on it to Done
  • All subitems’ Status columns should update automatically to Done


Sync values only for subitems that meet a condition

Automation recipe:
“When parent item column changes, and only if subitem status/label is something, copy that value to this subitem column”
What it doesUpdates subitems only if they meet a specific Status or Label condition.
Best use caseUse this when some subitems should follow the parent item, while others should remain unchanged.
Example
  • Parent item Due Date changes
  • Only subitems with Status = Not Started should receive the new Due Date
  • Subitems marked Done should not be updated


Sync values based on subitem name

Automation recipe:
“When subitem is created and if the subitem's name is this name set the value of its column to match the value of column in its parent item.”
What it doesCopies a value from the parent item only when the subitem has a specific name.
Best use caseUse this when only certain types of subitems should inherit values.
Example
  • Subitems named “Review” should inherit the parent item’s Reviewer
  • Other subitems (e.g., Design, QA) should not


Sync values only if the subitem column is empty

Automation recipe:
“When subitem is created, set the value of its column to match the value of column in its parent item, only when the subitem column is empty.”
What it doesCopies a value from the parent item only if the subitem column has no value.
Best use caseUse this when users sometimes manually fill subitem values and you don’t want automations to overwrite them.
Example
  • Parent item has a Priority
  • If a subitem already has a Priority set manually, leave it unchanged
  • If it’s empty, inherit the parent item’s Priority


Set the subitem name based on a parent item column

Automation recipe:
“When subitem is created, change its name to the value of this column in its parent item.”
What it doesUses a parent item column value as the subitem’s name.
Best use caseUse this when subitems should always be named after a specific parent item value.
Example
  • Parent item has a Client Name column
  • Every subitem should automatically be named after the client


Add the parent item name as a prefix or suffix

Automation recipe:
“When subitem is created, add name of its parent item as a prefix to its name with this connector”
What it doesAppends or prepends the parent item name to the subitem name.
Best use caseUse this when subitems are viewed outside their parent context and need clearer identification.
Example
  • Parent item: Website Redesign
  • Subitem: Design
  • Final name: Website Redesign – Design


Copy a mirror column value from the parent item

Automation recipe:
“When subitem is created, copy the value from its parent item mirror column to this column”
What it doesCopies values from a Mirror column on the parent item into a subitem column.
Best use caseUse this when parent items pull data from connected boards and subitems also need that information.
Example
  • Parent item mirrors Account Manager from a CRM board
  • New subitems should automatically receive the same Account Manager


Copy connected item names into a subitem Text column

Automation recipe:
“When subitem is created copy the name/s of the connected items in the parent item’s connected column to the subitem’s text column.”
What it doesCopies the names of connected items from the parent item into a Text column on the subitem.
Best use caseUse this when subitems need a static reference to connected items without maintaining live connections.
Example
  • Parent item is connected to multiple Vendors
  • Subitems should store vendor names as text for reporting or exports


Need help choosing the right automation?

Each recipe is designed for a specific timing or condition. If you’re unsure which one fits your workflow, start by asking:
  • Do I want this to run on creation or updates?
  • Should all subitems be updated or only some?
  • Should existing values be overwritten or preserved?
If you still need help, reach out to our support team and we’ll help you configure the best setup for your board.
  • Email:  support@fantasymedia.io