# monday.com Confirmed Status Auto-Create Items on Another Board Canonical: https://www.taskrhino.ca/en-us/monday-com-automations/status-auto-create-items/ > When a monday.com status changes to Confirmed, auto-create an item on another board: what native automations map, where AND-only conditions stop, fixes. Published: 2026-02-26 Updated: 2026-10-29 Author: Rakesh Patel Categories: BoardBridge **Key takeaways** - A monday.com custom automation can create an item on another board when a status changes, with “only if” conditions that are AND-ed (e.g., Confirmed AND Show + Travel). - OR logic and branching need the workflow builder (If/Else, multi-branch); board automations can’t express them. - Column mapping works only for columns that exist on both boards; Dependency, Link to Item and Time Tracking columns don’t map. - Each board can hold 10,000 linked items (100,000 on Enterprise), with a warning at 80%. - The workflow builder covers what board automations can’t: If/Else and multi-branch for OR logic, Find connected item for data on another board. **Here’s the pain point:** A band member confirms attendance, and the system should auto-generate travel, accommodation, and production items — but ONLY for confirmed members, ONLY for travel-required events, and ONLY with the right data mapped to each board. monday.com’s [native cross-board automations](https://www.taskrhino.ca/en-us/monday-com-automations/cross-board-limitations/) don’t fully support this. Status changes can create items, and a custom automation can add “only if” conditions (like dropdown = “Travel Required”), but board automations can’t branch or use OR logic. And they map only columns that exist on both boards. You’ve confirmed a team member’s attendance for an event. Their status changes from “Pending” to “Confirmed” on your Confirmations board. You need the system to automatically create a travel item on your Travel board — with their name, airport, flight time, and any special requirements pre-filled. That’s not a “nice-to-have.” It’s the difference between a scalable workflow and manual data entry. **The monday.com limitation:** Native [cross-board automations can create items](https://www.taskrhino.ca/en-us/monday-com-automations/data-transfer-between-boards/) on other boards. That part works fine. But they hit a wall with **compound conditions** beyond simple AND (OR logic and branching). You can say: “When status = Confirmed **AND** event type = Travel Required, create travel item” — custom automations AND their “only if” conditions. You can’t say “**OR**” in a board automation. You can’t check either of two conditions in a board automation (see [compound conditions](https://www.taskrhino.ca/en-us/monday-com-automations/if-then-conditional/)): OR and branching need the workflow builder (If/Else, multi-branch). And monday.com doesn’t document in detail how status and dropdown labels map between boards, so check that values transfer correctly. TaskRhino tip Create the item once, on the first status change, then keep it in sync with Connect Boards and Mirror columns instead of creating it again on every update. The result? Every status change triggers an automation, and anything its conditions can’t express slips through. You get duplicate travel items, items with wrong data, and a ton of manual cleanup. **What you actually need:** - ✓ Compound trigger conditions (status **AND** dropdown, status **AND** date, etc.) - ✓ Dynamic column value mapping (pull 5+ column values from the source item and populate the new item correctly) - ✓ Status/dropdown mapping by text (matching labels by name across boards) - ✓ Template-based item creation that survives board duplication - ✓ Multiple target boards in one automation (one status change, create items on 3 different boards) ## Real-World Example: Confirmed → Create Travel Item with Flight Data Let’s walk through a specific use case: event production with band members and crew. ### The Workflow **Board 1: Band Confirmations** - Columns: Name, Email, Confirmation Status, Event Type, Departure Airport, Flight Time Preference, Dietary Restrictions **Board 2: Travel Bookings** - Columns: Traveler Name, Email, Departure Airport, Arrival Airport, Outbound Flight Time, Return Flight Time, Special Requests **Desired automation:** - When a band member’s Confirmation Status changes to “Confirmed” - **AND** Event Type dropdown = “Show + Travel” - **THEN** create a new item on the Travel Bookings board with: - Traveler Name ← Band member’s Name from Confirmations - Email ← Email from Confirmations - Departure Airport ← Departure Airport from Confirmations - Arrival Airport ← Venue airport (from Event Overview board) - Outbound Flight Time ← Flight Time Preference from Confirmations - Special Requests ← Dietary Restrictions from Confirmations **This is a typical production workflow** for event companies. ## The monday.com Limitation: No OR Logic in Cross-Board Automations monday.com’s native cross-board automations support basic triggers: - “When status changes to X, create item on Board Y” - “When item is created, create item on Board Y and connect boards” **What board automations can and can’t do:** - “When status = X **AND** dropdown = Y, create item” (works: custom automations take several “only if” conditions, which are AND-ed) - “When status = X **OR** status = Z, create item” (not in a board automation; needs a workflow with If/Else or multi-branch) **Official monday.com documentation on cross-board automations:** > “In order to map across boards, the column you want to map must exist on both boards.” This allows simple column-to-column mapping, but it doesn’t support: - OR logic or branching (that needs the workflow builder) - Dynamic column value transformation (e.g., “If dropdown = ‘Show + Teebox’, set arrival airport to ‘Golf Resort Airport'”) - Multi-step conditional logic ([Source: monday.com Support – Cross-board automations](https://support.monday.com/hc/en-us/articles/360011393900-Cross-board-automations)) ### Community Evidence: Users Need Compound Conditions **Thread: “Issue with Cross-board automations for subitems” (February 2024)** User describes needing “a certain status of the subitem changes **and** the two items are connected” as a compound trigger. monday.com’s automation center doesn’t support this. (Source: monday.com Community Forum) **Thread: “Multi-board Status update via Automation” (May 2023)** User wants status on Board A to trigger actions on Board B, but **only when certain other conditions are met**. Board automations covered only part of this at the time. (Source: monday.com Community Forum) **Thread: “Is it possible to automatically create an item on a board when statuses on two separate boards are changed?” (November 2021)** > “I am creating a sequenced set of boards in which an item will be processed in one board, work its way through, and when done, an item will be created on the next board. At one point in the sequence, items will be created based on statuses from TWO different source boards.” — Is it possible to automatically create an item on a board when statuses on two separate boards are changed to a specific value? **The pattern:** Users are asking for multi-column, multi-board condition logic at least since 2021. monday.com’s answer came in the workflow builder (If/Else, multi-branch, Find connected item), not in board automations. See more gaps like this in our [monday.com automations](https://www.taskrhino.ca/en-us/monday-com-automations/) guides. **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 The confirmation → travel workflow fits a native custom automation as long as every condition is AND-ed and every mapped column exists on both boards. 1. **Pick the trigger:** on Band Confirmations, start a custom automation with “When status changes to something” and choose “Confirmed”. 2. **Add the condition:** add “and only if” Event Type is “Show + Travel”. Further “only if” conditions are AND-ed. 3. **Create the item:** choose “create an item in board” and pick Travel Bookings. 4. **Map the columns:** map Name, Email, Departure Airport, Flight Time Preference and Dietary Restrictions to their Travel Bookings columns; each column must exist on both boards. 5. **Test it:** set a test item to Confirmed and check that each value arrived, including status and dropdown labels. **Where it stops:** the Arrival Airport lives on a third board (Event Overview), and an OR (“Confirmed” or “Waitlist Approved”) can’t go in one board automation. Both need the workflow builder: Find connected item fetches the venue’s airport, and If/Else or multi-branch puts a Create item step in each branch. **Result:** Travel item created with the mapped data pre-filled. If you’d rather have the workflow built for you, we can set it up as one of our [custom monday.com builds](https://www.taskrhino.ca/en-us/monday-com-customization/). Wondering whether BoardBridge fits this workflow? [Ask us](https://www.taskrhino.ca/en-us/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 vs OR Logic ### AND Logic (All Conditions Must Be True) **Example 1: Confirmed AND Travel Required:** - Condition 1: Status = “Confirmed” - Condition 2: Event Type = “Show + Travel” - Logic: AND - Result: Item created only if BOTH conditions are true **Example 2: Confirmed AND Contact Details Present:** - Condition 1: Status = “Confirmed” - Condition 2: Email is not empty - Logic: AND - Result: Prevents creating travel items without contact details ### OR Logic (Any Condition Can Be True) **Example 1: Multiple Status Triggers:** - Condition 1: Status = “Confirmed” - Condition 2: Status = “Waitlist Approved” - Logic: OR - Result: Item created if EITHER status is set **Example 2: Emergency OR Priority:** - Condition 1: Priority dropdown = “Emergency” - Condition 2: Status = “Critical” - Logic: OR - Result: Triggers urgent notification if either condition is met ### Mixed Logic (Nested AND/OR) **Example:** (Status = Confirmed AND Event Type = Travel) OR (Priority = Emergency): normal confirmed travelers or any emergency cases. **monday.com limitation:** Board automations AND their conditions but have no OR and no nested logic; branching needs the workflow builder. Definition **Static column:** a column type monday.com can’t map when an automation creates or moves an item across boards: Dependency, Link to Item and Time Tracking. ## Column Mapping in Native Cross-Board Automations **What native mapping needs:** - The column must exist on both boards before it can be mapped. - Dependency, Link to Item and Time Tracking columns can’t be mapped. - Static columns (like Files) don’t show the blue “+” mapping indicator. - Status and dropdown labels aren’t documented in detail, so test that values transfer. Key stat 10,000 linked items is the most one board can hold on Basic, Standard and Pro (100,000 on Enterprise); monday.com warns at 80%. ## Board Automations vs the Workflow Builder: Side-by-Side Comparison | Feature | Board Automations (Custom) | Workflow Builder | | --- | --- | --- | | **Single-condition triggers** | ✓ Yes (status = X, item created) | ✓ Yes | | **AND conditions (2+ criteria must be true)** | ✓ Yes (“only if” conditions) | ✓ Yes | | **OR conditions (any criterion can be true)** | No | ✓ Yes (If/Else, multi-branch) | | **Nested AND/OR logic** | No | ✓ Yes (branches) | | **Condition operators** | Varies by column | Goes beyond equals (Smart condition) | | **Column value mapping across boards** | Columns that exist on both boards | Create item steps inside each branch | | **Cross-board data retrieval** | No | ✓ Yes (Find connected item, Find matching item) | | **Automation survives board duplication** | Recipes duplicate; remapping of cross-board targets not documented | Not documented | ## What Compound Conditions Unlock ### 1\. Multi-Criteria Workflows Real-world workflows often require checking multiple conditions before taking action. **Example: Event confirmation workflow** - Only create travel items for confirmed attendees (Status = Confirmed) - Only for events that require travel (Event Type = Show + Travel OR Show + Teebox) - Only for future events (Event Date > Today) With board automations alone, the OR in the event type means separate automations or a workflow, and the future-date check needs a workflow Smart condition. ### 2\. Reduced Noise and False Triggers Compound conditions prevent automations from firing when they shouldn’t. **Example: Client notification workflow** - Send “project complete” email only when Status = Done **AND** all deliverables are uploaded (File Column is not empty) - Without AND logic, you’d send the email when status changes to Done even if files aren’t ready ### 3\. Complex Business Logic Without Workarounds When business rules have multiple criteria, you can express them directly in automation logic instead of inventing workarounds. **Example: Priority escalation workflow** - Escalate to manager when Priority = High **AND** Days Overdue > 3 - Escalate to director when Priority = Critical **OR** Client Type = Enterprise - Board automations can’t express the OR; a workflow with If/Else can ### 4\. Cross-Board Intelligence Compound conditions can reference data from multiple boards. **Example: Budget approval workflow** - Create finance approval item when Budget Amount > $10,000 (from Project Board) **AND** Client Tier = Enterprise (from CRM Board) - Requires pulling data from 2 different boards: the workflow builder’s Find connected item step can fetch it, and number thresholds need workflow conditions To change a status on another board instead of creating an item, see [updating a status on another board with a button click](https://www.taskrhino.ca/en-us/monday-com-automations/button-update-status-another-board/). **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 **Why does my cross-board automation create duplicate items every time a date or status field updates on the source board?** ### monday.com’s native automation logic treats every field change as a new trigger event, so if you’re using ‘create item when status changes’ combined with date updates, it fires the create action repeatedly rather than updating the existing linked item. To prevent duplicates, create the item once (triggered by initial status change) and then use Connect Boards + Mirror columns to sync subsequent updates, or consider third-party solutions like Same Item Multiple Boards that maintain a single source of truth across boards. **Can I create conditional cross-board automations that check multiple criteria before creating an item—like ‘create only if status is confirmed AND event type is travel-required’?** ### Partly. A custom automation can add several “only if” conditions, which are AND-ed, so “create only if status is confirmed AND event type is travel-required” works natively. OR logic and branching need the workflow builder (If/Else, multi-branch, Smart condition), where Create item steps can sit inside each branch. Condition steps count toward your automation actions. **What happens when I try to map data fields to items being auto-created on another board—which column types won’t transfer?** ### When mapping columns during cross-board item creation, monday.com does not currently support mapping for Dependency, Link to Item, and Time Tracking columns. Additionally, static columns (like Files) won’t show the blue ‘+’ mapping indicator, and you must ensure the column exists on both the source and destination boards before mapping will work. **If I automate item creation across multiple boards based on a single status change, will I hit monday.com’s linkage limits, and how do I monitor for it?** ### Possibly. A board can hold 10,000 linked items on Basic, Standard and Pro (100,000 on Enterprise), with 750 per cell. monday.com sends a bell and email warning at 80% (8,000 links) and stops new links at 100%. Each auto-created connection adds a link on both boards, so a board that gets one linked item per deal grows by one link per deal; watch the busiest boards and archive old connections before they reach the limit. **Can I use mirror columns to trigger automations on the destination board when data syncs from the source board?** ### Mostly no. monday.com says most mirror columns can’t trigger automations, but a mirrored status column works in a few templates: when status changes, notify someone; start or stop time tracking; and change another status. For anything else, trigger the automation on the source board, where the original column changes. **How do I handle subitem-to-item cross-board automation when monday.com doesn’t natively support it?** ### monday.com currently cannot connect subitems to items via cross-board automation—you can only connect items to subitems, not the reverse. Additionally, Connect Boards columns created at the subitem level don’t appear as options in automation templates. To work around this architectural limitation, you’ll need to either restructure your data hierarchy or use third-party apps that can bridge this gap, though security-restricted environments may require a native monday.com solution that doesn’t yet exist.