# monday.com Automation Target Specific Group on Board

Canonical: https://www.taskrhino.ca/en-us/monday-com-automations/target-specific-group/

> monday.com doesn’t document picking a group when an automation creates an item on another board. Here’s how to land items in the right group natively.

Published: 2026-02-26  
Updated: 2026-10-29  
Author: Rakesh Patel  
Categories: BoardBridge

**Key takeaways**

-   monday.com doesn’t document choosing a group when a cross-board automation creates an item; community answers report the top group.
-   The native fix is two steps: create the item, then a “move item to group” automation on the target board places it.
-   The API’s create\_item mutation accepts a group ID, so your own integration can create items straight into a group.
-   “Create an item” has no duplicate check; a workflow can check first with Find matching item, but that check is board-wide.
-   Routing by data takes one move automation per group, or a workflow with If/Else or multi-branch conditions.

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](https://www.taskrhino.ca/en-us/monday-com-automations/cross-board-limitations/); our [monday.com automations guide](https://www.taskrhino.ca/en-us/monday-com-automations/) 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?

Definition

**Group:** a section of a board that holds related items, like a category or bucket; every item sits in exactly one group.

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:** Canceled (canceled 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](https://support.monday.com/hc/en-us/articles/360011393900-Cross-board-automations)). The API’s `create_item` mutation does accept a group ([monday.com developer docs](https://developer.monday.com/api-reference/reference/items)), 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](https://community.monday.com/t/duplication-of-items-in-the-same-board-between-groups/110743)

**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](https://community.monday.com/t/auto-copy-items-from-one-board-to-another/71321)

**Need help with cross-board 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)

## How to Place Items in the Right Group Natively

### Option 1: Create, Then Move

1.  **Create the item:** on Band Confirmations, a custom automation: when status changes to “Confirmed”, and only if Event Type is “Show + Travel”, create an item in Travel Bookings, mapping a Travel Direction column.
2.  **Move it:** on Travel Bookings, a second automation: when an item is created, and only if Travel Direction is “Outbound”, move item to group “Outbound Travel”.
3.  **Repeat per group:** add one move automation for each other group (Return Travel, Canceled Travel), or one workflow with multi-branch conditions.
4.  **Test:** confirm a test band member and check that the new item ends up in “Outbound Travel”.

TaskRhino tip

Map the column that decides the group (here, Travel Direction) onto the target board, so the move automation there can read it.

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](https://www.taskrhino.ca/en-us/contact-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](https://www.taskrhino.ca/en-us/monday-com-automations/preventing-duplicate-items/).

**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)

## 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

| Feature | monday.com Native Automations | Your Own API Integration |
| --- | --- | --- |
| **Create item in a specific group** | Not documented; create, then move with a second automation | `create_item` takes `group_id` |
| **Find a group’s ID** | N/A | Query the board’s groups (id, title) |
| **Duplicate prevention (board-wide)** | Workflow Find matching item | Query first (no API dedupe mutation) |
| **Duplicate prevention (group-aware)** | Not documented (key-column workaround) | Query the target group’s items first |
| **Dynamic group routing based on conditions** | Workflows (If/Else, multi-branch); board automations need one per condition | Your code picks the group |
| **Move item between groups (same board)** | ✓ Yes (“move item to group”) | ✓ Yes |
| **Works after board duplication** | Group names preserved; cross-board references not documented | Look up group IDs by title on each 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)

## 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, Canceled

**Target board:** Travel Bookings

-   Groups: Outbound Travel, Return Travel, Canceled 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](https://www.taskrhino.ca/en-us/monday-com-automations/dont-carry-over-duplicated-boards/)).

For which column values carry over to the new item, see [column copying between boards](https://www.taskrhino.ca/en-us/monday-com-automations/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](https://www.taskrhino.ca/en-us/monday-com-automations/button-update-status-another-board/).

Need the routing built for you? Our [monday.com customization](https://www.taskrhino.ca/en-us/monday-com-customization/) team can set up the automations, workflows or an API integration.

## Frequently Asked Questions

**How does group name resolution work?**

### 

Native automations don’t document group selection for created items, so there’s nothing to resolve: a move automation names the group you pick. In your own integration, query the board’s groups (id and title), find the title you want, and pass that ID as group\_id to create\_item.

**What if I rename a group after setting up the automation?**

### 

Check each automation that names the group after renaming it; monday.com doesn’t document how a rename affects them. In your own integration, look the group up by title each time, or store its ID.

**Can I create items in multiple groups from one automation?**

### 

Not directly: monday.com doesn’t document a group choice on the create action. Create the items, then let move automations on the target board place each one by a column such as Travel Direction, or use the API, where each create\_item call takes its own group\_id.

**What’s the difference between group-aware and board-wide duplicate prevention?**

### 

Board-wide: “If John Smith exists anywhere on the board, don’t create.” Result: John appears once in Outbound Travel, but Return Travel item isn’t created. Group-aware: “If John Smith exists in the Outbound Travel group, don’t create. If John exists in Return Travel group, don’t create. But John can exist in both groups.” Result: John appears in both groups (once each).

**Can I prevent duplicates across multiple columns (Name + Email)?**

### 

Find matching item looks up an item by a column value, so for Name + Email use a text key column that combines both and check that. In your own integration, query items with a rule for each column before creating.

**What if the target group is deleted?**

### 

monday.com doesn’t document what a “move item to group” automation does when its group is deleted, so check the automation after deleting groups. In your own integration, check that the group exists before creating the item.

**Does group-aware duplicate prevention work with subitems?**

### 

Not by group: subitems have no groups of their own and sit under a parent item.

**Can I move items between groups as their status changes?**

### 

Yes. Automation: “When status changes to X, move item to group Y.” This is a single-board action and works natively. To move an item to another board, use the “move item to board” action.

**How do I test group routing before going live?**

### 

Create a test item for each route and check where it lands; each automation’s Run history shows how it ran. monday.com has no preview mode (see [monday.com’s missing dry-run mode](https://www.taskrhino.ca/en-us/monday-com-automations/dry-run/)).

**Can I route items to different groups based on dropdown values?**

### 

Yes, with one move automation per dropdown value on the target board, or one workflow with multi-branch conditions: if Trip Type = “Outbound”, move the item to “Outbound Travel”; if Trip Type = “Return”, move it to “Return Travel”.

## 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 canceled 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](https://www.taskrhino.ca/en-us/contact-us/) if you want it built.