Using the 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 that sync parent item values to subitems, explains , and provides so you can choose the best option for your setup.
These automations automatically copy values 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 .
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
Below is a breakdown of each automation recipe, exactly as it appears in Monday.com , along with recommended use cases.
Copies a column value from the parent item to the subitem .
Use this when you want every new subitem to automatically inherit a value from the parent item, but you .
- Parent item has an
- Every new subitem should automatically get the same owner
- Existing subitems should remain untouched if the owner later changes
Updates the selected column on whenever the parent item’s column changes.
Use this when subitems must always stay in sync with the parent item, even after creation.
- Parent item Status changes from Working on it to Done
- All subitems’ Status columns should update automatically to Done
Updates subitems .
Use this when some subitems should follow the parent item, while others should remain unchanged.
- Parent item changes
- Only subitems with Status = Not Started should receive the new Due Date
- Subitems marked Done should not be updated
Copies a value from the parent item .
Use this when only certain types of subitems should inherit values.
- Subitems named should inherit the parent item’s Reviewer
- Other subitems (e.g., Design, QA) should not
Copies a value from the parent item .
Use this when users sometimes manually fill subitem values and you don’t want automations to overwrite them.
- Parent item has a
- If a subitem already has a Priority set manually, leave it unchanged
- If it’s empty, inherit the parent item’s Priority
Uses a parent item column value as the .
Use this when subitems should always be named after a specific parent item value.
- Parent item has a column
- Every subitem should automatically be named after the client
Appends or prepends the parent item name to the subitem name.
Use this when subitems are viewed outside their parent context and need clearer identification.
- Parent item: Website Redesign
- Subitem: Design
- Final name: Website Redesign – Design
Copies values from a on the parent item into a subitem column.
Use this when parent items pull data from connected boards and subitems also need that information.
- Parent item mirrors from a CRM board
- New subitems should automatically receive the same Account Manager
Copies the names of connected items from the parent item into a on the subitem.
Use this when subitems need a static reference to connected items without maintaining live connections.
- Parent item is connected to multiple
- Subitems should store vendor names as text for reporting or exports
Each recipe is designed for a . If you’re unsure which one fits your workflow, start by asking:
- Do I want this to run on or ?
- Should be updated or only some?
- Should existing values be ?
If you still need help, reach out to our support team and we’ll help you configure the best setup for your board.