Send to Storage

Last Updated: May 19, 2026

The Storage step in Workflow routes files into Vasion Storage or an integrated third-party storage provider as part of an automated workflow. The file saves to the folder location configured in the workflow. If a document event triggers the workflow, the following metadata is automatically captured and stored with the file: Created date, file size, file type, page count, and last modified date. The metadata is searchable on the Storage page and appears in the Details section when you view the file in Storage.

Key Points

Review the following key points:

  • Third-party storage destinations are available only if the admin configured the integrations.
  • If the admin turned on an integration but you have not connected your account, the Storage step shows a prompt to complete the connection before you can select a destination folder.
  • A Storage step supports one destination. To route a file to more than one destination, use a Split step with a separate Storage step in each branch.
  • If you have more than one account configured for the same third-party storage provider, each account appears as a separate option in the step.
  • Subfolder creation in third-party storage providers is not available. You can select only existing folders as destinations.
  • Existing workflows that use Vasion Storage as their destination do not require additional steps.
  • Access to stored files is governed by the permissions on the selected destination folder. No additional file or metadata permissions are applied.

How Send to Storage Works

When you configure a Storage step, you select a storage provider and a destination folder. The Select Folder modal shows only folders you have access to, including shared folders.

When the workflow runs, the system validates that the destination folder exists and is accessible before transferring the file. If validation fails then the workflow stops at the Storage step and an error appears. If the file transfer fails after validation, the system retries up to three times before stopping and logging the failure.

If a file with the same name already exists in the destination folder, the provider's native behavior applies, such as versioning or overwriting.

Requirements

Review the following requirements:

  • Send to Storage requires Workflow licensing. Contact your Vasion representative for details.
  • You need a third-party storage provider integration if you are using Google Drive, OneDrive, or SharePoint. For more details refer to Integrations and Connect Storage Providers.
  • You need a folder location configured in the storage provider.
  • You must have permission to edit the workflow and access the destination folder in Vasion Storage.

Related Topics

Refer to the following: