TL;DR: Connection and sync automations specifically for items ↔ subitems across boards. Most "item/subitem" recipes from the other categories work here too — this category focuses on the subitem-specific patterns and setup considerations that don't apply to item-to-item flows.
When to use these automations
You want to connect a subitem on this board to an item (or subitem) on another board
You want subitem-level workflows to sync across boards — not just the parent item
You have a parent-child hierarchy on this board that needs to mirror or react to records on another board
Before you start
Subitems must be enabled on the source board. Add the Subitems column from the board settings if it isn't already there.
A Connect Boards column on the entity you want to connect (item or subitem level)
For sync recipes: matching columns on both sides must have the same name and type
Subitem webhooks are broader than item webhooks — review Understanding webhooks for what that means in practice
What you can build
1. Connect a subitem to its match on another board
The "item/subitem" variants of the connect recipes can target subitems specifically — connect a new subitem to an item, to a subitem on the parent board, or to a subitem on a different board.
Use when: parent items live on one board but the detail-level tasks live as subitems and need to link to records on another board (e.g. project ↔ task-level dependencies).
2. Connect + Sync between subitems across boards
The Two-way sync recipes accept all four entity combinations: Item↔Item, Item↔Subitem, Subitem↔Item, Subitem↔Subitem. Use the same recipe with subitem selected as the entity to set up cross-board subitem sync.
Use when: task-level details should stay aligned across two boards — not just the parent.
3. Connect subitems with fuzzy "contains" matching + ongoing sync
When a new item or subitem is created here, auto-connect to items/subitems on another board whose column contains the matching value (not exact equals), then keep matching columns synced two-way. Useful when matching keys have prefixes, suffixes, or surrounding noise.
Use when: matching values aren't perfectly clean (e.g. "CUST-12345" needs to match "Customer ID: 12345" elsewhere) and you also want ongoing two-way sync.
Connect subitems by column-contains match and keep them synced two-way
Setup considerations specific to subitems
Subitem webhooks fire more often than item webhooks.monday.com sends one webhook per subitem column change; the recipe filters internally. This is normal and harmless to your quota.
The connect column lives on the entity you're connecting. If you want to link subitems, the connect column must be on the subitem level (added through the subitem settings) — not on the parent item.
Same-name-and-type still applies. Subitem-to-subitem sync needs matching columns on both subitem schemas.
Common gotchas
Don't confuse subitem connect columns with parent connect columns. They're separate columns on different entities.
Subitem recipes can't write to parent-level connect columns (or vice versa). Pick the recipe that targets the correct entity.
Subitem creation order matters for some flows. If a recipe expects an existing parent, ensure the parent item exists before subitems are created.