monday.com Confirmed Status Auto-Create Items 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 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 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): 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.

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)

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 guides.

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.

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. Wondering whether BoardBridge fits this workflow? Ask us.

Compound Conditions: AND vs OR Logic

AND Logic (All Conditions Must Be True)

OR Logic (Any Condition Can Be True)

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.

Column Mapping in Native Cross-Board Automations

Board Automations vs the Workflow Builder: Side-by-Side Comparison

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.

Frequently Asked Questions