# monday.com Status Change Cross-Board Trigger Canonical: https://www.taskrhino.ca/monday-com-automations/status-change-cross-board-trigger/ > How to trigger cross-board actions from monday.com status changes, using automations that create items, update boards and sync data across workspaces. Published: 2026-02-26 Updated: 2026-10-29 Author: Rakesh Patel Categories: BoardBridge **Key takeaways** - monday.com’s “When status changes to something” trigger fires only on the label you pick, and custom automations can add AND-ed conditions before creating an item on another board. - OR logic, branching and data-driven group routing need one automation per case or a workflow (If/Else, multi-branch). - Dependency, Link to Item and Time Tracking columns can’t be mapped; users also report Location columns not copying. - Most mirror columns can’t trigger automations; a mirrored status works only in a few templates. - For several cases in one place, or data from a connected board, use the workflow builder (If/Else, multi-branch, Find connected item). Status changes to “Confirmed” on your Confirmations board. Your team needs to know. Logistics needs to start planning. The Production board needs a new item created with details from the confirmation. **In monday.com, you have three choices:** 1. **Manually create the item on the Production board** — copy-paste the details 2. **Set up a cross-board automation** — it fires only on the label you choose and can add AND conditions, but has no OR logic or branching 3. **Use Connect Boards + Mirror columns** — but they’re read-only, and most mirror columns can’t trigger automations **What you actually need:** Status change on Board A → creates item on Board B, **but only when [specific conditions are met](https://www.taskrhino.ca/monday-com-automations/if-then-conditional/)** (e.g., only when Type = “VIP Client” AND Status = “Confirmed”). ## Cross-Board Status Triggers Need Conditional Logic Here’s what teams need: **When status changes on Board A:** - Create an item on Board B (with data from Board A) - But only when OTHER conditions are also met: - Status = “Confirmed” AND Type = “Outbound” - Status = “Approved” AND Priority = “High” - Status = “Ready” AND Department = “Production” **What monday.com offers:** monday.com’s native “cross-board create item” automation (see [cross-board automation limitations](https://www.taskrhino.ca/monday-com-automations/cross-board-limitations/)) has these limitations: 1. **AND only** — you can trigger on a status change and add conditions like “AND dropdown = X”, but all conditions are AND’ed; OR logic and branching need a workflow (If/Else, multi-branch) 2. **Limited column types for match triggers** — dropdown columns can’t be the column change trigger in match automations 3. **No conditional routing in one automation** — sending items to different groups on Board B by Board A data takes an automation per condition, or a workflow with If/Else or multi-branch 4. **Column mapping restrictions** — Dependency, Link to Item and Time Tracking columns can’t be mapped; users report Location columns don’t copy **The result:** Teams build separate automations to handle different combinations, build workflows, or resort to manual work. ## What monday.com Users Are Saying **Thread: Match automations need dropdown menus as column change trigger** — 2023 monday.com’s “match” automations only support specific column types as triggers. **Dropdown columns are excluded** from the column change trigger selector. **Thread: Create item in another board — location column not copying** — April 2025 > “When I try to create an item via automation from 1 board to a second board, location columns on the source board don’t appear to be supported to copy to the second board.” — **julDH14 (Julie H)**, April 1, 2025 No monday.com staff response. monday.com’s docs don’t list Location as unsupported, but users report it doesn’t copy in [cross-board column mapping](https://www.taskrhino.ca/monday-com-automations/data-transfer-between-boards/). **Official monday.com documentation confirms** ([Cross-board automations – monday.com Support](https://support.monday.com/hc/en-us/articles/360011393900-Cross-board-automations)): **Unsupported column types for cross-board mapping:** - Dependency - Link to Item - Time Tracking Location and Dropdown problems come from community posts, not the docs. **Columns supported in match templates:** Item name, People, Date, Status, Numbers, Timeline, Link, Phone, Email, Text, Priority, Label **No OR logic** — you can add conditions via the “+” button, but all conditions are AND’ed together. You cannot create OR logic in a board automation; workflows add If/Else and multi-branch. Dropdown columns are excluded only as the column change trigger in **match automations**, not from cross-board automations generally. ## Additional Cross-Board Issues (Subitems & Dropdown Reliability) **Thread: Issue with Cross-board automations for subitems — February 2024** > “When a certain status of the subitem changes a new item is created into another board and the two items are connected. Monday already provides an automation like that, but it seems that the automation **creates the new item and then it creates a new connection column, but it does so in the parent structure of the board, not in the subitem.**“ **Issue:** Subitem cross-board automations create connections at the parent item level, not the subitem level. Data doesn’t sync properly when subitems are involved. **Thread: Automations to add or remove a dropdown item between boards — August 2024** > “Automations are unable to do **cross-board data mirroring that triggers a drop down item** to be added or deleted from another board.” — **nataliecanestro**, August 15, 2024 **Issue:** Users report dropdown values not transferring as expected in cross-board workflows, especially when the dropdown options don’t match exactly between boards. **Third-party tool notes ([MoveoBoost: Advanced Automation for monday.com](https://www.moveoboost.com/post/advanced-automation-monday-com-autoboost)):** > “Mirror Columns Show Static Data: Mirror columns display the current linked item data, but do **not trigger automations when that data changes**.” **Implication for cross-board triggers:** monday.com’s own help says most mirror columns can’t be automation triggers; a mirrored status works only in a few templates (notify someone, start or stop time tracking, change another status). Trigger cross-board item creation from the source board instead. **Plan Your Cross-Board Workflow** Get help setting up the automations, conditions and column mapping for every new item. [Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## How to Build It in monday.com ### Option 1: One Custom Automation per Case - **Automation 1:** When status changes to “Confirmed”, and only if Type is “Outbound”, create an item in the Travel board - **Automation 2:** When status changes to “Confirmed”, and only if Type is “Return”, create an item in the Travel board Each automation maps the columns that exist on both boards, such as Date and Destination. monday.com doesn’t document choosing a group for the new item, so a “move item to group” automation on the Travel board places it in “Outbound Travel” or “Return Travel” (see [targeting a specific group](https://www.taskrhino.ca/monday-com-automations/target-specific-group/)). ### Option 2: One Workflow with Branches In the workflow builder, one status trigger can feed If/Else or multi-branch conditions on Type, and each branch gets its own Create item step. ### Option 3: Build It Yourself with the API **Step 1: Status Change Webhook** Definition **Webhook:** a message monday.com sends to another server when a column changes, saying which item, which column and what the new value is. Your integration subscribes to the Band Confirmations board with a webhook. When the status column changes, the webhook sends which item, which column and what the new value is. **Step 2: Check the Conditions** If the new value is “Confirmed”, your code fetches the item and checks the other conditions: ``` // Fetch the full item data from monday.com const item = await getItemColumnValues(itemId); // Check the Type dropdown if (item.type_dropdown === "Outbound") { // This rule matches } ``` **Step 3: Create Item on Target Board** If all conditions match, create an item on the Travel board: ``` mutation { create_item( board_id: 1234567890, group_id: "outbound_group", item_name: "Alex Johnson - Outbound Travel", column_values: "{\"date_column\": {\"date\": \"2026-03-15\"}, \"type_status\": {\"label\": \"Outbound Travel\"}, \"destination_text\": \"Chicago\"}" ) { id } } ``` Wondering whether BoardBridge fits this workflow? [Ask us](https://www.taskrhino.ca/contact-us/). **Need help structuring your monday.com boards?** Book a free 30-minute call with a certified monday.com partner. [Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## Compound Conditions: AND Logic You can configure multiple conditions that must ALL be true for the action to fire: **Example:** - Status = “Confirmed” - **AND** Type = “VIP Client” - **AND** Priority = “High” Only when all three conditions are true does the cross-board item creation fire. **Why this matters:** Native board automations also AND their conditions, but each combination that leads to a different action is a separate automation: - Automation 1: Status = Confirmed + Type = VIP → Action - Automation 2: Status = Confirmed + Type = Standard → Different Action - Automation 3: Status = Confirmed + Type = VIP + Priority = High → Another Action So the number of automations grows with the number of cases; a workflow with branches keeps them in one place. ## Conditional Group Routing Teams want items to land in different groups on the target board based on source item data: **Example:** **When:** Status = “Confirmed” **AND:** Type = “Outbound” **Then:** Create item in the “Outbound Travel” group **When:** Status = “Confirmed” **AND:** Type = “Return” **Then:** Create item in the “Return Travel” group monday.com doesn’t document choosing a group when a cross-board automation creates an item; community answers report the top group and suggest a “move item to group” automation on the target board, one per group, or a workflow with multi-branch conditions. ## Column Mapping: What Transfers Native cross-board automations map columns that exist on both boards; Dependency, Link to Item and Time Tracking can’t be mapped, and users report Location columns not copying. **Why this matters:** label IDs differ from board to board, and monday.com doesn’t document how its own cross-board mapping handles status and dropdown labels, so test that values arrive as expected. ## Real-World Example: Event Confirmations → Travel Board **Confirmations Board columns:** - Name: “Alex Johnson” - Status: “Confirmed” - Type: “Outbound” (Dropdown) - Date: March 15, 2026 - Destination: “Chicago” **When status changes to “Confirmed”:** 1. The Outbound automation’s “only if” condition checks the Type dropdown 2. Type = “Outbound” → the condition passes 3. The automation creates an item on the Travel board, mapping the columns that exist on both boards: - Item name: “Alex Johnson” - Date: March 15, 2026 - Destination: “Chicago” 4. A move automation on the Travel board moves it to the “Outbound Travel” group **Result:** Zero manual item creation. Travel team sees the new travel item instantly. ## Multiple Actions Per Trigger One status change can trigger multiple cross-board actions: **When:** Status = “Confirmed” **Actions:** 1. Create item on Travel board 2. Create item on Production board 3. Update status on Master Dashboard 4. Send email to logistics team All four actions run from one trigger, one after another; the automation’s conditions apply to all of them (see [one trigger, multiple actions](https://www.taskrhino.ca/monday-com-automations/one-trigger-multiple-actions/)). ## Limitations You Should Know TaskRhino tip Add a guard status such as “Travel Created” and an “and only if” condition on it, so an item that flips back to Confirmed doesn’t create a second travel item. **OR logic needs a workflow.** Board automations AND their conditions; for “Status = A OR Status = B,” build two automations or a workflow with If/Else. **Data from a connected board needs a workflow.** A board automation maps only the trigger item’s own columns; the workflow builder’s Find connected item step can fetch the rest. Our [monday.com automations guide](https://www.taskrhino.ca/monday-com-automations/) lists the other limits. **Group placement takes a second step.** monday.com doesn’t document a group choice for created items; a move automation on the target board places each one. Need a workflow like this built? Our [monday.com customization](https://www.taskrhino.ca/monday-com-customization/) team can set it up, or [ask us](https://www.taskrhino.ca/contact-us/) whether BoardBridge fits. **Need Help With Your monday.com Setup?** TaskRhino has implemented monday.com for 110+ teams. Get a free consultation. [Schedule Free Consultation](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## Frequently Asked Questions **How can I trigger creation of a Production board item only when status changes to ‘Confirmed’ on Confirmations board, without firing on every status update?** ### monday.com’s native “When status changes to Confirmed” trigger already fires only on that label, and a custom automation can add AND-ed “only if” conditions before “create an item in board”. Map the columns that exist on both boards in the same automation. **Why do native monday.com cross-board automations create duplicate items on my Production board for every status change instead of just ‘Confirmed’?** ### They shouldn’t: the “When status changes to something” trigger fires only on the label you pick, and custom automations can AND extra conditions. If you see an item for every change, check that the trigger names the Confirmed label rather than any column change. Mirror columns won’t help here: most can’t trigger automations. **Can I use Connect Boards with mirror columns to auto-create and populate Production items from Confirmations board status ‘Confirmed’ changes?** ### Mostly no. Mirror columns display data from the connected board, and most can’t trigger automations; a mirrored status works only in a few templates (notify someone, start or stop time tracking, change another status), none of which creates an item. Trigger the creation from the Confirmations board with a status-change automation. **What’s the best way to copy multiple column values from a ‘Confirmed’ item on Confirmations board to a new Production board item automatically?** ### Native cross-board automations can create the item when status changes to Confirmed, add AND-ed conditions, and map columns that exist on both boards (Dependency, Link to Item and Time Tracking can’t be mapped). For a value from a third board, use a workflow with Find connected item. This avoids manual copy-paste. **How to avoid duplicate Production items when using automations triggered by any status change on Confirmations board?** ### monday.com’s native status trigger fires each time an item changes to the chosen label, so an item that moves back to Confirmed creates another item, and “when column changes” triggers fire on every change. Add a guard: have the same automation set a “Travel Created” status, and add an “and only if” condition that it isn’t set yet, so the item is created once. See [preventing duplicate items](https://www.taskrhino.ca/monday-com-automations/preventing-duplicate-items/) for more patterns. **Is there a monday.com automation to create connected items on Production board with full details only on ‘Confirmed’ status from Confirmations board?** ### Yes: the native “When status changes to Confirmed, create an item in board and connect them” automation fires only on Confirmed and maps columns that exist on both boards, though complex data mapping is harder. For data from another board, a workflow’s Find connected item step can fetch it.