Move Folder

Audience: Business Users

Skill Prerequisites: Tokens

Moves a folder, including all its files and subfolders, into another folder. The folder keeps its name. The new location is saved as tokens for use by the actions that follow.

Typical Use Cases

• Move a project folder to an Archive folder when the project is closed
• Move uploaded files from a staging folder into their final location after approval
• Reorganize folder structures as part of an automation

Don't use it to

• Rename a folder. Use Rename Folder instead.
• Move a single file. Copy it with Copy File and then remove the original with Delete File.

Related Actions

Action Name	Description
Get or Create Folder	Makes sure the destination folder exists before moving into it.
Rename Folder	Changes the name of a folder without moving it.
Delete Folder	Deletes a folder.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Folder to move	The folder to move, as a folder ID or a path relative to Portals/<PortalID>/ (for example Projects/Apollo/).	Yes	empty string	Yes
Folder to move to	The destination folder, as a folder ID or a path relative to Portals/<PortalID>/. The destination must already exist. Leave empty to move the folder to the portal root.	Yes	Portal root	No

Output Parameters Reference

Parameter	Description
Output Token Name	The name of the token that stores details of the moved folder. See the tokens in the next table.

If Output Token Name is Moved, the following tokens are created:

Token	Description	Example
[Moved:FolderId]	The folder ID. It's the same ID as before the move.	212
[Moved:FolderPath]	The new folder path, relative to the portal root.	Archive/Apollo/
[Moved:PhysicalPath]	The new physical path of the folder on the server.	C:\inetpub\site\Portals\0\Archive\Apollo\

Considerations

• Permissions. Administrators can move any folder. Other users need copy permission on the folder being moved and add permission on the destination folder, otherwise the action fails.
• URLs change. The path of every file inside the folder changes, so any saved URL or path that points to those files stops working. Links that use the file ID keep working.
• Destination must exist. The action fails if either folder can't be found. Use Get or Create Folder first if needed.
• A folder can't be moved into itself or into one of its own subfolders.

Examples

tip

To understand how to use the below examples, please see Running Examples.

1. Archive a project folder

The first action makes sure Archive/ exists. The second action moves Projects/<ProjectCode>/ into it and saves the new path in [ArchivedProject:FolderPath].

[
    {
        "Title": "Get or Create Folder",
        "ActionType": "GetOrCreateFolder",
        "Description": "Make sure the Archive folder exists",
        "Condition": null,
        "Parameters": {
            "FolderPath": {
                "Expression": "Archive",
                "Value": "",
                "IsExpression": true,
                "Parameters": {}
            },
            "FolderMappingConnection": {
                "Expression": "",
                "Value": "",
                "IsExpression": false,
                "Parameters": {}
            },
            "OutputTokenName": "ArchiveFolder"
        }
    },
    {
        "Title": "Move Folder",
        "ActionType": "MoveFolder",
        "Description": "Move the project to the archive",
        "Condition": null,
        "Parameters": {
            "SourceFolderIdentifier": "Projects/[ProjectCode]/",
            "DestinationFolderIdentifier": "[ArchiveFolder:FolderId]",
            "OutputTokenName": "ArchivedProject"
        }
    }
]

Revised 09/25/2026