Node: Move to Group

The Move to Group node automatically relocates a task (item) on a Board into a different group on the same board — exactly as if an agent had dragged the card by hand. It's the standard action for reflecting status changes in a kanban-style flow (e.g. moving a card from "In Progress" to "Done") without manual work.

When to use it

• In workflows triggered by Board events (item created, column changed, etc).
• As the final step of a flow that creates or updates a task and needs to place it in its definitive group.
• Combined with the create_item node in Inbox/AI flows that first create a task and then need to sort it onto the board.

Requirements

• The workflow must run with a board item in context (triggered from a Board, or with an item created earlier in the same flow). If there's no item in context, the node is skipped silently.
• The destination group must exist on the same board as the item.
• Doesn't apply to subitems — only top-level rows can be moved.

Configuration

• Destination group (group_id, required): the board group the item will move into. When the editor has board context, you pick it from a dropdown of existing groups; in a chat/AI flow, you supply the numeric group ID directly.

Example

A workflow fires when a Support board's "Status" column changes to "Resolved". The next step is a Move to Group node targeting the "Closed" group, so the card relocates itself without the agent dragging it.

Tips

• If the item is already in the destination group, the node is a safe no-op — you can re-run it without side effects.
• Pair it with create_item when an Inbox flow converts a conversation into a task and needs to drop it in the right group from the start.

Troubleshooting

• "group not on board": the configured group_id belongs to a different board. Confirm the group exists on the item's board.
• Node keeps getting skipped: check that the workflow's trigger actually delivers a board item in context, or that a create_item step ran earlier in the same flow.