monday.com Status Change Cross-Board Trigger

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 — but it creates items without conditions, triggering on every status change
3. Use Connect Boards + Mirror columns — but they’re read-only and don’t trigger actions

What you actually need: Status change on Board A → creates item on Board B, but only when specific conditions are met (e.g., only when Type = “VIP Client” AND Status = “Confirmed”).

Boards Pain Point #15 + Automation Pain Point #1: 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 has these limitations:

1. Single condition only — you can trigger on status change, but you cannot add a second condition like “AND dropdown = X”
2. Limited column types for triggers — dropdown columns cannot be used as triggers in cross-board automations
3. No conditional routing — you cannot send items to different groups on Board B based on Board A data
4. Column mapping restrictions — Dependency, Link, Time Tracking, Location columns do not transfer

The result: Teams build 10+ separate automations to handle different combinations, or resort to manual workflows.

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. Location columns are not supported in cross-board column mapping.

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

Dropdown column values do not reliably transfer cross-board.

Official monday.com documentation confirms (Cross-board automations – monday.com Support):

Unsupported column types for cross-board mapping:

• Dependency
• Link to Item
• Time Tracking
• Location (undocumented) Source
• Formula, Mirror (read-only)
• Dropdown (unreliable) Source

Supported types: Item name, People, Date, Status, Numbers, Timeline, Link, Phone, Email, Text, Priority, Label

No compound conditions — you can add conditions via the “+” button, but all conditions are AND’ed together. You cannot create OR logic. And critically, you cannot combine a status trigger with a dropdown condition because dropdown columns are not available as trigger types in cross-board automations.

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. Dropdown column values do not reliably transfer cross-board.” — nataliecanestro, August 15, 2024

Issue: Dropdown options are unreliable in cross-board workflows. Values that transfer successfully from one board may not transfer to another, especially if the dropdown options don’t match exactly by name or ID.

Third-party tool notes (MoveoBoost: Advanced Automation for monday.com):

“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: If you try to use Mirror columns as a trigger source for cross-board automations, they won’t fire because mirror columns are read-only and don’t register changes.

How BoardBridge Solves This

BoardBridge’s conditional cross-board trigger workflow allows you to create items on Board B based on status changes on Board A, with full conditional logic:

Example: Travel Item Creation

Trigger Board: Band Confirmations Target Board: Travel

Rule:

• When: Status changes to “Confirmed”
• AND: Dropdown “Type” = “Outbound”
• Then: Create an item on the Travel board with:
• Item name from Band Confirmations
• Date from Confirmations → Travel Date
• Type → “Outbound Travel”
• Destination from Location column

Different rule:

• When: Status changes to “Confirmed”
• AND: Dropdown “Type” = “Return”
• Then: Create an item on the Travel board with:
• Item name from Band Confirmations
• Date from Confirmations → Travel Date
• Type → “Return Travel”

Result: One status change on the Confirmations board can trigger different actions on the Travel board depending on the Type dropdown value.

How It Works

Step 1: Status Change Webhook

BoardBridge monitors the Band Confirmations board via a webhook. When any column changes, the webhook fires with details about which item, which column, and what the new value is.

Step 2: Evaluate All Conditional Rules

The system queries all workflow rules configured for the Confirmations board where:

• trigger = "status_change"
• column = "confirmation_status"
• value = "Confirmed"

For each matching rule, the system checks if additional conditions are met:

“`javascript // 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:

“graphql mutation { create_item( board_id: "travel_board_id", group_id: "outbound_group", item_name: "Alex Johnson - Outbound Travel", column_values: { "date_column": "2026-03-15", "type_status": "{\"label\":\"Outbound Travel\"}", "destination_text": "Chicago" } ) } “

Step 4: Log the Action

The system logs which rule fired, which item was created, and on which target board. This appears in the admin panel for audit and debugging.

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: With native monday.com, you’d need separate automations for every combination:

• 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

With compound conditions, you define one rule with multiple AND conditions instead of managing 10+ separate automations.

Conditional Group Routing

Items can be created 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

Native monday.com cross-board automations let you specify a target group, but it’s static — you can’t dynamically route to different groups based on data.

BoardBridge evaluates the source item data and selects the target group conditionally.

Column Mapping with Type Safety

BoardBridge maps column values between boards with proper type formatting:

Text columns: Plain string Status columns: {label: "text"} format, resolving label text to the correct status ID on the target board Dropdown columns: Same as status — text label resolution Date columns: ISO 8601 date string Number columns: Numeric value Email columns: {email: "address", text: "display name"}

Why this matters: Monday.com uses different internal IDs for status labels on different boards. If you try to copy a status ID from Board A to Board B, it fails. BoardBridge maps by text label, which resolves correctly across boards.

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. BoardBridge evaluates the Type dropdown
2. Type = “Outbound” → rule matches
3. Creates item on Travel board:

• Item name: “Alex Johnson – Outbound Travel”
• Travel Date: March 15, 2026
• Type: “Outbound Travel” (Status)
• Destination: “Chicago”

1. Item appears in 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 actions fire from one trigger, with independent conditional logic per action.

Limitations You Should Know

Dropdown and status conditions require exact text matches. If your dropdown has “VIP” but you configure the condition to check for “Vip” (different capitalization), it won’t match. Text matching is case-sensitive.

OR logic is not supported. All conditions are AND’ed together. If you need “Status = A OR Status = B,” you’d create two separate rules.

Connect Boards columns are not supported as data sources for mapping. If you need to pull data from a connected item, you’d use Mirror columns on the source board first.