monday.com Automation Target Specific Group on Board

When you create a new item on a monday.com board via automation, you want control over which group it lands in. If you’re creating a travel booking, it should go into the “Outbound Travel” group, not the “Lodging” group. If you’re adding a confirmed band member to a roster, they should appear in the “Confirmed” group, not “Pending.”

The monday.com limitation: Native cross-board automations create items without a documented way to pick the target group; community answers suggest a separate “move item to group” step. You can’t choose “create item in the ‘Confirmed’ group” dynamically from item data in one simple automation. And “create an item” has no built-in duplicate check, group-aware or otherwise; a workflow can check first with Find matching item. This is one of many monday.com cross-board automation limitations; our monday.com automations guide covers the rest.

What you actually need:

• Create items in specific groups by name (not just the default group at top)
• Group-aware duplicate prevention (same item can appear in multiple groups, but not twice in one group)
• Dynamic group routing (conditions determine which group an item lands in)
• Multiple automations handling different group targets from one source board

The monday.com Group Limitation: Items Go to Default Group

What Are Groups on monday.com?

Groups are organizational sections within a board. They’re like “categories” or “buckets” for items.

Example board: Band Confirmations

• Group 1: Pending (band members who haven’t responded)
• Group 2: Confirmed (band members who confirmed attendance)
• Group 3: Declined (band members who declined)
• Group 4: Cancelled (cancelled attendees)

Use case: When a band member’s status changes to “Confirmed,” you want to move them from “Pending” group to “Confirmed” group.

What monday.com’s Native Automations Can Do

monday.com’s automation center includes a “Move item to group” action:

• “When status changes to X, move item to group Y”
• You manually select the target group from a dropdown

This works for single-board item movement. But it doesn’t work for cross-board item creation.

The Cross-Board Creation Limitation

When you use a cross-board automation like “When status changes on Board A, create item on Board B,” monday.com’s docs don’t say which group the item lands in on Board B or describe a group picker; community answers report the top group and suggest a separate move step.

monday.com’s cross-board automations article doesn’t mention groups at all (monday.com Help Center). The API’s create_item mutation does accept a group (monday.com developer docs), so any limit is in the automation builder, not the platform.

Community Evidence: Users Need Group-Specific Item Creation

Thread: “Duplication of Items in the same Board (between Groups)” (March 2025)

User describes automation creating items hundreds of times:

“When it comes to duplicating items within the same Board and having them move to a different Group, my automation runs steady and copies my item hundreds of times and will not stop until I turn off the automation – what I want is only one duplication (per group), and it auto-moved to its corresponding group.”

The user wants group-aware duplicate prevention — create one item per group, not hundreds.

Source: monday.com Community

Thread: “Auto-copy items from one board to another” (November 2023)

User wants to copy roster items from one board to another into specific groups based on item properties. The thread didn’t surface a native one-step way to do this.

Suggested workaround: Use monday.com’s “move item to group” automation after creating the item. This requires two separate automations (one to create, one to move), which is inefficient and creates a brief moment where the item is visible in the wrong group.

Source: monday.com Community

How to Place Items in the Right Group Natively

Option 1: Create, Then Move

The item sits in the top group for a moment before it moves, which is the inefficiency community answers describe.

Option 2: Your Own Integration with the API

The API’s create_item mutation takes a group_id, so an integration can create the item straight into the right group. Look up the group IDs by title first:

query {
  boards(ids: 987654321) {
    groups {
      id
      title
    }
  }
}

Then create the item in that group:

mutation {
  create_item(
    board_id: 987654321,
    group_id: "group_abc123",
    item_name: "John Smith - Outbound Travel",
    column_values: "{}"
  ) {
    id
  }
}

Wondering whether BoardBridge fits your group routing? Ask us.

Group-Aware Duplicate Prevention

The Problem: Board-Wide Duplicate Prevention Isn’t Enough

monday.com’s API has no dedupe mutation: create_item doesn’t check for existing items. The usual pattern is to check first (an API query, or a workflow Find matching item step) and create the item only if no match exists on the board.

Example:

• Check if an item with Name = “John Smith” already exists on the Travel board
• If yes, skip creation
• If no, create the item

The limitation: A simple “does it exist on the board?” check is board-wide, not group-specific.

Real-world scenario where board-wide duplicate prevention fails:

Travel board has 2 groups:

• Outbound Travel
• Return Travel

Workflow:

• Automation 1: When band member confirmed → create “John Smith” in Outbound Travel group
• Automation 2: Later, when return flight booked → create “John Smith” in Return Travel group

With board-wide duplicate prevention:

• Automation 1 creates “John Smith” in Outbound Travel
• Automation 2 checks if “John Smith” exists on the board → Yes (in Outbound Travel group)
• Automation 2 skips creation → Return Travel item is NOT created

What you actually need: “John Smith” can exist once in Outbound Travel AND once in Return Travel, but not twice in the same group.

A Group-Aware Check, Natively

monday.com doesn’t document a group filter for Find matching item. One workaround is a text key column that combines the name and the group (for example, “John Smith |⁠ Outbound”), filled in when the item is created; a workflow’s Find matching item then looks for that key before creating, so the same person can exist once per group. In your own integration, query the items in the target group first. More patterns in preventing duplicate items in monday.com automations.

Dynamic Group Routing Based on Conditions

You can route items to different groups based on column values.

Example 1: Outbound vs Return Travel Routing

On the Travel board (after the item is created there):

• When an item is created, and only if Travel Direction is “Outbound” → move item to group “Outbound Travel”
• When an item is created, and only if Travel Direction is “Return” → move item to group “Return Travel”

Result: Items move to the correct group based on the Travel Direction dropdown value.

Example 2: Priority-Based Routing

On the Task Board:

• Priority = “Critical” → move item to “Urgent” group
• Priority = “High” → move item to “This Week” group
• Priority = “Normal” → move item to “Backlog” group

Result: One move automation per priority, or one workflow with multi-branch conditions.

Example 3: Status-Based Group Movement

On Band Confirmations:

• Status changes to “Confirmed” → move item to “Confirmed” group
• Status changes to “Declined” → move item to “Declined” group
• Status changes to “Canceled” → move item to “Canceled” group

Result: Items automatically move between groups as their status changes (one automation per status).

Native Automations vs the API: Side-by-Side Comparison

How to Set Up Group-Specific Item Creation

Here’s a step-by-step guide:

Step 1: Identify Your Boards and Groups

Source board: Band Confirmations

• Groups: Pending, Confirmed, Declined, Cancelled

Target board: Travel Bookings

• Groups: Outbound Travel, Return Travel, Cancelled Travel

Step 2: Build the Create Automation

On Band Confirmations: when status changes to “Confirmed”, and only if Event Type is “Show + Travel”, create an item in Travel Bookings. Map Name, Email, Departure Airport, Flight Time Preference and Travel Direction (each column must exist on both boards).

Step 3: Build the Move Automations

On Travel Bookings: when an item is created, and only if Travel Direction is “Outbound”, move item to group “Outbound Travel”. Add one per group.

Step 4: Guard Against Duplicates

Have the create automation also set a “Travel Created” status on the band member, with an “and only if” condition that it isn’t set yet, so flipping the status back to Confirmed doesn’t create a second item.

Step 5: Test

• Create a test item on Band Confirmations, set Event Type to “Show + Travel” and Travel Direction to “Outbound”
• Change Confirmation Status to “Confirmed”
• Verify the item appears on Travel Bookings, moves to “Outbound Travel” and has the right column values
• Change the status to “Pending” and back to “Confirmed”: no second item

Step 6: After Duplicating Boards

If you duplicate both boards for a new project, repoint the create automation to the new Travel Bookings board and check the move automations (see cross-board recipes that break on duplication).

For which column values carry over to the new item, see column copying between boards; to update a status on another board from a button, see updating a status on another board with a button click.

Need the routing built for you? Our monday.com customization team can set up the automations, workflows or an API integration.

Frequently Asked Questions

Final Thoughts: Organization Starts with Placement

When you create 100 travel items per project, you don’t want all 100 landing in the default group at the top of the board. You want outbound travel in one group, return travel in another, and cancelled bookings in a third.

Items should land in the correct group from the moment they’re created—not in a catch-all group that requires manual sorting.

monday.com doesn’t document a target-group option for native cross-board item creation, and the common workaround is two steps (create item, then move item), which is inefficient and creates a moment where items appear in the wrong place.

Until monday.com documents a group option, use a move automation on the target board, or the API’s group ID. Ask us if you want it built.