Search K
Appearance
Vault Add File
The Vault Add File node uploads a local file into Autodesk Vault, adding it to a specified Vault folder.
Purpose
Use this node to automate file uploads to Vault, enabling seamless integration of local file generation or downloads with Vault document control workflows.
Inputs
| Field Label | Input Type | Description |
|---|---|---|
| Local File Full Path | Text | The full local file path of the file to upload to Vault. |
| Folder Identifier | Text | The identifier of the Vault folder where the file should be added. |
Outputs
This node does not create explicit output variables but updates Vault with the newly added file, making it available for subsequent Vault operations in the workflow.
Functionality
This node:
- Validates required inputs (
Local File Full Path,Folder Identifier). - Retrieves service account tokens for Autodesk Vault and general Autodesk authentication.
- Establishes a Vault connection using these service accounts.
- Validates the local file exists at the specified path.
- Retrieves the Vault folder by its identifier.
- Uploads the local file to Vault, adding it to the specified folder with a comment “File Added With MinuteView Automations.”
Example Use Case
✅ Upload a PDF report generated earlier in the workflow to a documentation folder in Vault.
✅ Add a newly created CAD file to a project folder in Vault as part of an automated release process.
Task Success Criteria
- Success: The file is uploaded successfully to the specified Vault folder.
- Failure: If Vault connection, local file validation, folder retrieval, or upload fails, the task returns a descriptive error message indicating the failure point.
Notes
- Ensure ServiceAccount-Autodesk Vault and ThirdParty-Autodesk service accounts are configured with valid credentials and have necessary upload permissions.
- The Folder Identifier must be valid and accessible within Vault for the upload to succeed.
- The file is added with no classification and a default comment. Adjustments to classification or comments may be implemented in future node versions if required.