# monday.com Button Click Update Status on Another Board Canonical: https://www.taskrhino.ca/en-us/monday-com-automations/button-update-status-another-board/ > monday.com buttons can’t update a status on another board with a ready-made recipe. The workflow route, the Connect Boards workaround and their limits. Published: 2026-02-26 Updated: 2026-10-29 Author: Rakesh Patel Categories: BoardBridge **Key takeaways** - monday.com has no ready-made recipe for “when a button is clicked, update the status of a linked item on another board”. - Classic cross-board recipes create or move items; Mirror columns show another board’s values read-only. - The workflow builder can do it with a Find connected item step and a status change, but a button click isn’t a documented workflow trigger. - A button can still start it indirectly: the button changes a local status, and a workflow watching that status updates the linked item. - Test any chain where one automation’s change is meant to start another: monday.com doesn’t document that it always will. You need a button that updates a status column on a **different board**. Click “Mark Complete” on the Booking board, and the corresponding item on the Delivery board changes status to “Ready to Ship”. No manual board-hopping, no copy-pasting item names. monday.com’s button column can trigger automations, and [cross-board automations do exist](https://www.taskrhino.ca/en-us/monday-com-automations/cross-board-limitations/). But here’s the problem: **classic cross-board recipes are designed to create items, move items, or mirror data — not to selectively update a status column on an existing linked item.** The result? Teams build fragile workarounds involving Connect Boards columns, Mirror columns, and intermediate status columns that cascade changes. Or they give up and manually update both boards. This article explains why monday.com’s cross-board architecture makes this harder than it should be, and the native routes that work. ## The Problem: Cross-Board Automations Are Create/Move-Focused monday.com’s cross-board [automation recipes](https://www.taskrhino.ca/en-us/monday-com-automations/) are built around **creating new items** or **moving existing items** from one board to another. The automation templates you see in the builder reflect this: - “When status changes, **create an item** on another board” - “When item is created, **move it** to another board” ### What’s Missing There’s no ready-made board recipe for: > “When button is clicked on Board A, **update the status column** on a linked item on Board B” Definition **Find connected item:** a workflow step that follows a Connect Boards column to the linked item on another board, so later steps can change that item. You can create items. You can move items. You can mirror column values (read-only). The workflow builder can do it: a Find connected item block locates the linked item through a Connect Boards column, and a later step changes its status ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/20598895919122-AI-Workflows-features-and-capabilities)), though monday.com’s docs don’t confirm a button click as a workflow trigger. In classic recipes, selectively updating a specific column on a linked item requires stitching together Connect Boards columns, Mirror columns, and automation triggers in ways that break easily. ### Documented Column Limits From the [official cross-board automations documentation](https://support.monday.com/hc/en-us/articles/360011393900-Cross-board-automations): **Unsupported column types in cross-board item creation:** - Dependency - Link to Item - Time Tracking Connect Boards has limits too: a board can connect to 1 board on Basic, 5 on Standard, 20 on Pro and 200 on Enterprise (up to 60 per column on Enterprise), with up to 10,000 connected items per board (100,000 on Enterprise) and 750 in one cell ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/360021743500-Linkage-limitations-for-the-Connect-Boards-Column)). For how the columns behave, see [Connect Boards and Mirror columns](https://www.taskrhino.ca/en-us/monday-com-forms/connect-boards-mirror-columns/). Even when you CAN create items cross-board, some column types don’t transfer. And **updating an existing item on another board** takes the workflow builder’s Find connected item or Find matching item blocks rather than a ready-made recipe. ## What Users Need vs. What monday.com Offers ### What Users Need | Scenario | Desired Workflow | | --- | --- | | Sales handoff | Click “Mark Won” on CRM board → Delivery board item status changes to “In Queue” | | Project milestone | Click “Design Approved” on Design board → Development board item status changes to “Ready to Build” | | Vendor confirmation | Click “Vendor Confirmed” on Booking board → Logistics board item status changes to “Confirmed” | | Multi-board workflows | Update status on 3 boards from one button (CRM, Delivery, Finance) | ### What monday.com Offers | Feature | Support | | --- | --- | | Cross-board item creation | ✅ Supported, but many column types don’t transfer | | Cross-board item move | ✅ Supported, but moves the entire item (doesn’t leave a copy) | | Cross-board status update via automation | ⚠️ No ready-made recipe; the workflow builder’s Find connected item block can do it | | Connect Boards + Mirror columns | ⚠️ Workaround exists but fragile and read-only on the mirrored side | | Button-triggered cross-board updates | ⚠️ Not as a ready-made recipe; a button-click workflow trigger isn’t documented | If you chain classic automations across boards — one automation’s change meant to start another — test the chain before relying on it: monday.com’s docs don’t say that a change made by an automation always starts the next one. Workflows avoid the question by chaining the steps in one run. ## Example: Sales to Delivery Handoff Take a company running a SaaS product delivery process. ### The Scenario The company uses two boards: 1. **CRM Board** — tracks deals through the sales pipeline 2. **Delivery Board** — tracks onboarding and implementation for won deals When a deal closes on the CRM board: - The sales rep clicks a **“Mark Won”** button - The system creates a corresponding item on the Delivery Board (company name, contact info, package type, start date) - The Delivery Board item’s status should automatically change to **“In Queue”** Later, when the delivery team assigns an onboarding specialist: - The delivery manager clicks an **“Assign Specialist”** button on the Delivery Board - The CRM Board item’s status should update to **“Onboarding Assigned”** (so sales reps can see progress) This is **bidirectional cross-board status sync** — changes on Board A reflect on Board B, and vice versa. ### The monday.com Approach (Workaround) Here’s the fragile workaround teams build: **Step 1: Connect the boards** - Add a **Connect Boards column** on the CRM board linking to the Delivery board - When the “Mark Won” button is clicked, an automation creates the Delivery Board item and populates the Connect Boards link **Step 2: Mirror the status** - Add a **Mirror column** on the CRM board to show the Delivery Board’s status - This is **read-only** — you can see the Delivery Board status, but you can’t change it from the CRM board **Step 3: Create intermediate status columns** - Add a **“Delivery Status Trigger”** status column on the CRM board - Try to set up an automation: When “Delivery Status Trigger” changes to “In Queue”, update the linked item’s status on the Delivery Board — there’s no classic action for that **Problems:** - **Mirror columns are read-only** — you can’t directly update the Delivery Board status from the CRM board - **Chained automations need testing** — monday.com doesn’t document whether a change made by one automation triggers the next one - **Column explosion** — you end up with “real” status columns and “trigger” status columns cluttering both boards - **Manual sync required** — when something breaks (and it will), someone has to manually update both boards ### A Native Route: Button + Workflow 1. **Link the boards.** Add a Connect Boards column on the CRM board linking each deal to its Delivery Board item. 2. **Button changes a local status.** A button automation on the CRM board: when “Mark Won” is clicked, change the “Handoff” status on the same item to “Won”. 3. **A workflow updates the linked item.** Trigger: when “Handoff” changes to “Won”. Steps: Find connected item on the Delivery Board, then an Update item step sets its Status to “In Queue”. No Connect Boards link? Find matching item finds the Delivery item by a shared value, such as a deal ID ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/20598895919122-AI-Workflows-features-and-capabilities)). 4. **Test the chain.** Click the button on a test item and check the Delivery Board: monday.com doesn’t document that a change made by an automation starts a workflow. 5. **Repeat in reverse.** For “Assign Specialist” on the Delivery Board, use the same pattern with a workflow that updates the linked CRM item. monday.com documents these blocks in its AI Workflows article, which lists the Pro and Enterprise plans, so check that your plan has them. For a status change that starts automations on a connected board, see [status-change cross-board triggers](https://www.taskrhino.ca/en-us/monday-com-automations/status-change-cross-board-trigger/). Each workflow step counts toward your monthly automation actions ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/360017556179-Automation-and-Integration-actions-and-limits)). **Need help with monday.com automations?** 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) ## The monday.com Workaround (Connect Boards + Mirror Columns) Here’s the most reliable monday.com-native workaround with Connect Boards and Mirror columns: ### Setup **On the CRM Board:** 1. Add a **Connect Boards column** linking to the Delivery Board 2. Add a **Mirror column** showing the Delivery Board’s status (read-only) 3. Add a **Status column** for your own CRM workflow stages **On the Delivery Board:** 1. Add a **Connect Boards column** linking back to the CRM Board (bidirectional link) 2. Add a **Mirror column** showing the CRM Board’s status (read-only) 3. Add a **Status column** for delivery workflow stages ### Automation 1: CRM → Delivery (Create Item) **Trigger:** When CRM status changes to “Won” **Action:** Create an item on the Delivery Board with: - Item name from CRM - Contact info from CRM - Package type from CRM - Connect Boards link back to the CRM item **Limitation:** Item-creating automations can map Status columns from the source item, but each mapped column counts as an extra action toward your quota ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/360017556179-Automation-and-Integration-actions-and-limits)). To set a fixed “In Queue” status, add a second automation on the Delivery Board (“When item is created, change status to ‘In Queue’”) or use a workflow with an Update item step after Create item. ### Automation 2: Delivery → CRM (Manual Sync) TaskRhino tip Before building the cross-board steps, add the Connect Boards link on every existing item. Find connected item can only follow links that are there. **Trigger:** When Delivery status changes to “Specialist Assigned” **Action:** ??? **Classic recipes have no action to update the linked CRM item’s status.** A workflow can: Find connected item, then change its Status column. Your options: - **Manual update** — someone opens the CRM board and changes the status - **Third-party integration** (Make.com, Zapier) — watches Delivery Board for status changes and updates CRM Board via API - **Mirror column only** — the CRM board shows a read-only Mirror of the Delivery status, but it’s not the “real” CRM status column None of these are clean. ## Get Help Setting It Up Want the native route built for your boards, or wondering whether BoardBridge fits this workflow? [Ask us](https://www.taskrhino.ca/en-us/contact-us/). ## When Native Cross-Board Automations Are Enough monday.com’s cross-board automations work perfectly fine when: - You need to **create a new item** on another board (e.g., sales deal → delivery project) - You’re okay **moving the entire item** to another board (not leaving a copy) - You don’t need **bidirectional status sync** - You’re fine with **read-only Mirror columns** showing cross-board data - Your workflow is **one-directional** (Board A → Board B, never B → A) For these cases, stick with native monday.com automations. **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) ## What This Means for Your Workflows Cross-board status updates eliminate manual board-hopping. In monday.com, the reliable route today is a workflow with Find connected item; a button can start it only through a status change you then test. For teams running multi-board workflows (sales → delivery → finance, booking → logistics → production, design → development → QA), the setup is worth getting right once. See also [cross-board recipes and duplicated boards](https://www.taskrhino.ca/en-us/monday-com-automations/dont-carry-over-duplicated-boards/) and [column copying between boards](https://www.taskrhino.ca/en-us/monday-com-automations/column-copying-between-boards/). ## Frequently Asked Questions **Can monday.com button columns update status on another board?** ### Not with a ready-made recipe. monday.com’s button automations can create items on another board or move items to another board, but there is no recipe for “update the status column of a linked item on Board B.” The workflow builder can do it with a Find connected item block and a status change, though monday.com doesn’t document a button click as a workflow trigger. Otherwise the workaround involves Connect Boards columns, Mirror columns, and intermediate status triggers — which is fragile and prone to breaking. **Can buttons trigger bidirectional updates?** ### Natively, with one workflow per direction: each uses Find connected item through the Connect Boards column to change the other board’s status. A button can start it only indirectly, by changing a status the workflow watches, so test that chain. **Does this consume monday.com automation quota?** ### Yes. Classic automations and workflows count toward your monthly automation actions (250 a month on Standard), and in a workflow each step counts.