Box - Move a file
The Box - Move a file action A tool for building the processes, logic, and direction within workflows. moves a file to from one folder to another folder in Box.

Box is a file synchronization and sharing service for businesses. Users upload files to their Box accounts and invite others to view and/ or edit their shared files. For more information on Box, see the company website.
In the context of Nintex Workflow Cloud, Box is a connector Service used to define a connection required for associated actions and start events. Examples include Salesforce and Box. Method of integration to cloud services, business applications and content stores.. For information on actions and start events available with Box, see Connectors.

While you can use Individual Box account connections Credentials and other settings required to pass data between the workflow and the indicated service, which could be a cloud service, business application, or content store. with Nintex Workflow Cloud, all features are only available when you use Enterprise account connections. See Box pricing for more information.

Variables allow you to store and manipulate data and files in your workflows. They can be created by start events, forms, tasks, workflow actions, or automatically created when a workflow is run. For more information, see Variables.

You can start a workflow whenever a new or updated file is detected (example: Box - New file), upload files on start or at any point in the workflow, generate documents from tagged templates, send and receive files via email, and manipulate files. You can set up file handling in your workflow start event The connector and event for triggering the workflow to run, including required configuration. An example is Box - New file, which triggers the workflow to run when a new file is uploaded to the specified folder. and actions A tool for building the processes, logic, and direction within workflows..
Note: Your tenancy's default file storage location must be configured to hold files for later reference by the workflow. This location is used for uploaded files and for files stored as output from actions.

- Start your workflow when a new or updated file is detected in a service; for example, see Box - New file and Connectors.
Store a file reference for use later in the workflow (file share connector start events)
File share connector start events, such as Box - New file, require you to add each start event variable that you want to reference later in the workflow. The variables provided vary by start event. See Connectors.
On the Designer canvas, click Start event.
Select a connector from the Start from drop-down list.
Select an event from the Event drop-down list.
- Click Add variables.
- Select the predefined variables that you want to add to your workflow. If you know the variable and you want to find it faster, type the variable name in the Filter options field. To select all variables, click Select All.
- Click Add.
Note: If you want to edit the selection of variables, hover over the variable, click
, and then click Show Details. Edit the variable name in the Name field or click
.
- Upload files when filling in a form from:
- Salesforce, using Nintex Drawloop DocAutomation for Salesforce
- The web or an app
-
Programmatically upload files for a Component workflow A workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.; see Nintex - Component workflow

- Generate documents from tagged templates using Generate document
- Send and receive files via email; for example, see Assign a task
- Manipulate files in services (see Connectors):
- Get, store, move, copy, or delete files using file share connector actions A workflow action that performs a basic operation through a connected system, such as Salesforce or Box., such as Box - Move a file
- Get and attach files in Salesforce
- Get and store files in SharePoint
- Get signatures: Get and store signed documents using DocuSign or Adobe Sign.
-
Store a file for use later in the workflow
For example, store any email attachments received by the task assignee.
- On the Designer canvas, click the action you want to configure.
-
Find the output field for storing the file or set of files.
For example, to store attachments received in task assignee email replies when they may attach multiple files, use the Assign a task Multiple file attachments option for the Store output field.
- In the output field, select a variable or specify a file path:
Select a variable. For outputs storing multiple files, select a collection variable. For outputs storing a single file, select a file variable.
Specify a file path. You can use any combination of text and variables, beginning with the root folder. If available, use the folder browse icon
on the right of the path field to navigate to the folder and any subfolders that you want, and then edit the path as desired to include variables and different text.
The availability of variable or path options for storing files varies by action. For more information, see Connectors and Workflow actions.
-
Reference a stored file
For example, reference the new Box file that started the workflow to attach it to a task email notification or reference an image received by the task assignee to generate an invoice document.
- On the Designer canvas, click the action you want to configure.
- Find the field where you want to reference the stored file select a variable or specify a file path:
Select the file variable associated with the stored file. For example, select the variable for the new Box file that started the workflow or select the variable storing Multiple file attachments output from a task action.
Specify the file path where the file is stored. You can use any combination of text and variables, beginning with the root folder. If available, use the folder browse icon
on the right of the path field to navigate to the folder and any subfolders that you want, and then edit the path as desired to include variables and different text.
View example
Both a file variable and a file path are used in the example image below for the Dropbox Business - Copy a file action. A file variable is selected for Source and a file path is specified for Destination.
The variables "CountryVariable" and "Program" insert the values into the file path as determined by earlier workflow logic (in this case, fields in a submitted form). For example, if the person submitting the form selects Australia for country and specifies Inspire2017 for program, then the resulting file path is "/SpecialProgramNDAs/Australia/Inspire2017NDA.docx."
Configure the Box - Move a file action
In the Designer page:
-
Click the Box action group in the action toolbox.
or
Find actions by browsing action groups, or by typing an action name or function in the Search field at the top of the action toolbox.
- Drag the Box - Move a file action to the point in the workflow when you want to move the file.
- Click the Box - Move a file action.
-
Select a Connection.
Don't have one yet? Follow these steps to create a Box connection
-
In the drop-down list for Connection, select Add new connection.
A new window appears, prompting you for a connection name.
- Type a user-friendly Connection name.
- Click Connect.
-
Enter credentials if prompted.
Upon successful log in, you are prompted to grant or deny access for Nintex Workflow Cloud.
-
Click the option to grant access.
A window appears where you can assign owner and user permissions to the connection. Add Owners and Users, if required. For more guidance on connection permissions, see Permissions.
- Click Save permissions.
The entered name is validated for uniqueness. If credentials are not stored in the browser for the selected connector service, then you are prompted for credentials. For more guidance on connections, see Connectors.
Your newly added connection now appears in the Connection field.
-
- Under Source, specify the file to move: Either select a file variable or type a file path. You can also browse the folder structure using the browse icon (
).
- Under Destination, in Path, type the file path where you want to move the file. You can also browse the folder structure using the browse icon (
).
- Select an option for Overwrite file.
For more information on the buttons and settings, see Box - Move a file action fields, buttons, and settings.
Maintain path integrity
Caution: If a file/folder that's used in a workflow is moved, renamed, or deleted, any workflows that use that file/folder will not start or will fail. Make sure you keep the paths in your workflow configurations up to date.

Section |
Field |
Description |
Variable types |
---|---|---|---|
(unlabeled) |
The Box connection to use for moving the file. |
(n/a) |
|
Source |
Select a source type |
Select how the action finds the file:
|
(n/a) |
|
File path |
Displays when you select the Path source type. The location in Box where the workflow retrieves the file from to move to the destination path. Accepts any combination of typed text, text added through navigation ( |
Text, Decimal, Integer, Boolean, DateTime |
|
File ID |
Displays when you select the File ID source type. The unique identifier number the action uses to access the file in Box. |
Text |
|
File variable |
The file to move to the destination path. Accepts an inserted variable. |
File |
Destination |
New file path |
The location in Box where the workflow moves the file to. Accepts any combination of typed text, text added through navigation ( |
Text, Decimal, Integer, Boolean, DateTime |
|
Overwrite file |
When selected, overwrites existing file with the same name in the destination. Accepts either a selection from the drop-down list or an inserted variable. |
Boolean |
|
Store file as a variable |
Variable to store the moved file. Accepts an inserted variable. |
File |
|
Store new file ID as a variable |
Variable to store the new file ID of the moved file. Accepts an inserted variable. |
Text |
|
Store new path as a variable |
Variable to store the path of the moved file. Accepts an inserted variable. |
Text |