move_item
Propose moving a page to a different collection or folder.
Last updated
move_item
Propose moving a page to a different collection, folder, or both. Queued for human approval unless the agent has auto-approve enabled.
At least one of target_collection_id or target_folder_id must be
provided. Calling with neither returns an immediate error — the move is
not submitted.
update_page covers the same capability; move_item is the clearer name
when the intent is purely relocation.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
page_id | string | yes | The ID of the page to move. |
target_collection_id | string | one-of | Move to this collection. |
target_folder_id | string | null | one-of | Move to this folder, or null to place at the collection root. |
Returns
Validation failure
If both target_collection_id and target_folder_id are omitted:
{
"isError": true,
"content": [
{
"type": "text",
"text": "move_item requires at least one of target_collection_id or target_folder_id."
}
]
}
Auto-approved
{
"content": [
{
"type": "text",
"text": "Page moved: note_xyz789 → collection=col_archive."
}
]
}
Awaiting approval
{
"content": [
{
"type": "text",
"text": "Move proposal submitted — awaiting approval in Plainwork. Action ID: act_abc123."
}
]
}
Example
Move to a different collection:
{
"tool": "move_item",
"arguments": {
"page_id": "note_xyz789",
"target_collection_id": "col_archive"
}
}
Move to the root of the current collection:
{
"tool": "move_item",
"arguments": {
"page_id": "note_xyz789",
"target_folder_id": null
}
}
See also
update_page— alternative API; also supports tag/title changeslist_collections