Integration: Upload Files to OneDrive (Microsoft)
The Upload Files to OneDrive node allows your workflow to automatically upload files directly to your Microsoft 365 account's OneDrive. When reaching this point in the flow, the instance sends the configured files — PDFs generated by previous nodes or files collected in forms — to the chosen destination folder, with no manual action required.
This node follows exactly the same behavior as the Upload Files to Google Drive node, but operates in the Microsoft ecosystem. If you already use Google Drive and know its configuration, you will find the same concepts here, just adapted for OneDrive and SharePoint.
The OneDrive node works the same way as the Google Drive node: same configuration options, same subfolder flow, same supported file types, and same 50 MB per file limit. The only difference is the account used — Microsoft instead of Google.
Prerequisite: Configure OneDrive Connection
Before adding this node to your workflow, you need to establish an authorized connection with your Microsoft 365 account. This connection is made once per workspace and is available for all workflows in the space.
- Access Settings in the side menu.
- Click on Integrations.
- Click on New connection and choose OneDrive (Microsoft).
- A Microsoft authentication window will open. Log in with the Microsoft 365 account that has the destination OneDrive.
- Grant the requested permissions for read and write to OneDrive.
- After authorizing, the connection will appear in the integrations list with the name of the associated Microsoft account.
Make sure the Microsoft account used has permission to write files to the chosen destination folder. Accounts with IT restrictions may not have write access to certain SharePoint drives or folders.
After the connection is created, it can be selected in any OneDrive node within the workspace workflows.
Node Configuration
When adding the Upload Files to OneDrive node to the canvas, a configuration panel will be displayed on the right side of the screen. Fill in the fields as described below.
| Field | Description | Required |
|---|---|---|
| OneDrive Connection | Select the Microsoft 365 connection previously configured in the workspace integrations. | Yes |
| Drive | Choose the drive available in the connected Microsoft account. Can be the user's personal OneDrive or a SharePoint drive they have access to. | Yes |
| Destination folder | Select the folder within the chosen drive where the files will be sent. The folder list is automatically loaded based on the selected drive. | Yes |
| Create subfolder per instance | Define whether each workflow execution should create an individual subfolder inside the destination folder. Options: Yes or No. | No |
| Subfolder name template | Available when the above option is Yes. Define the subfolder name using free text and variables in the format {{variable}}, such as Order {{order_number}} - {{customer_name}}. The name is resolved at execution time with the instance data. | Conditional |
| Artifacts to upload | Select the PDFs generated by previous workflow nodes (such as approval or email sending nodes) that should be included in the upload. | No |
| Upload form files | Choose the upload fields from ancestor forms whose files should be sent to OneDrive along with the other configured files. | No |
Enabling the Create subfolder per instance option is highly recommended when the workflow processes multiple records. With the name template using variables like {{customer_name}} or {{protocol_number}}, each instance will have its own folder automatically organized in OneDrive, with no risk of mixing files between different executions.
Types of Files Uploaded
The node supports two types of file sources that can be combined in the same execution:
Workflow-generated artifacts
These are PDFs automatically created by previous nodes during execution. For example, an Approval node generates a PDF with the record of the decision made by approvers. A Send Email node can also generate an artifact with the content of the sent email. These artifacts are available for selection in this field.
Form files
These are the files uploaded by respondents in upload-type questions within Hashdata forms. When the workflow is triggered by a form response that contains upload fields, those files can be selected here and will be forwarded to OneDrive as part of the instance processing.
The limit is 50 MB per file. Files that exceed this limit will not be sent and the instance will record an upload error for that file. Make sure that the forms associated with the workflow have maximum size validation configured.
Differences from Google Drive
The Upload Files to OneDrive node is functionally equivalent to the Upload Files to Google Drive node. The existing differences are exclusively related to the destination platform:
| Aspect | Google Drive | OneDrive (Microsoft) |
|---|---|---|
| Required account | Google account (Google Workspace or personal) | Microsoft 365 account (corporate or personal) |
| File destination | Google Drive (My Drive or Shared Drive) | Personal OneDrive or organization SharePoint |
| Authentication type | Google OAuth | Microsoft OAuth |
| Subfolder behavior | Identical | Identical |
| Limit per file | 50 MB | 50 MB |
| Supported file types | Identical | Identical |
| Node output | SINGLE_OUTCOME (always advances) | SINGLE_OUTCOME (always advances) |
If your organization uses the Microsoft 365 ecosystem as a standard, the OneDrive node is the natural choice for archiving and sharing documents generated by workflows. For organizations that use both platforms, it is possible to add both nodes in the same workflow to send copies to both Google Drive and OneDrive.
Behavior During Execution
When the workflow instance reaches the Upload Files to OneDrive node, the following happens:
- The system authenticates to the Microsoft account using the configured connection.
- The selected drive is accessed and the destination folder is located.
- If the subfolder option is active, a new folder is created with the name resolved from the template and instance variables.
- The selected files (artifacts and/or form files) are sent one by one to the destination folder.
- After uploading all files, the instance automatically advances to the next workflow node.
The node has a single output (SINGLE_OUTCOME), which means the flow always continues after execution, regardless of the number of files sent. Upload errors for specific files are recorded in the instance history, but do not interrupt the flow.
Usage Tips
- Combine with the Set Status node right after the upload to record in the instance that the files were successfully sent to OneDrive.
- Use date variables in the subfolder name template to organize files by period, such as
{{year}}-{{month}} - {{customer_name}}. - Position the node at the end of the workflow when the goal is to archive all documents generated during the process. This way, the artifacts from all previous nodes will already be available for selection.
- Check the destination folder permissions in SharePoint before publishing the workflow, especially in corporate environments with restricted access policies.