Scan destinations define where scanned documents are delivered after processing. OptimiDoc supports a wide range of destination types covering internal storage, local and network folders, cloud services, and custom integrations. Destinations and print connectors share one underlying model; this page covers the destinations available to scan templates.
Screenshot: Scan Destinations list view
How Delivery Works
For each destination on a scan template, OptimiDoc builds the matching storage connector and runs the same delivery sequence:
-
Connect -- OptimiDoc verifies it can reach the target (credentials, OAuth tokens, path) and prepares the connection.
-
Upload -- each output document, and any metadata file, is sent to the destination.
-
Commit -- the delivery is finalised.
Storage-style destinations (Folder, FTP, WebDAV, SharePoint, SharePoint Online, OneDrive, Google Drive, Dropbox, Box, S3-Wasabi) upload each file immediately as it is produced. Batch-style destinations (Email, OptimiDoc, Script) collect the documents first and act once at the commit step -- composing and sending the e-mail, storing the scan in OptimiDoc, or invoking the script.
Primary and Secondary Destinations
Each scan template has one primary destination, which is mandatory and receives every scan. A template can add any number of secondary destinations, each set to run:
-
Always -- deliver to this destination on every scan; or
-
On errors -- deliver only when the primary destination fails, so scans are never lost.
Destinations are assigned in the template's Output Options tab. Configuring an On errors secondary destination -- for example the OptimiDoc destination or a Folder -- gives you a safety net for less reliable targets. Scan destinations do not carry access rights of their own; visibility is governed by the scan template.
Available Destination Types
|
Destination |
Description |
|---|---|
|
Send scanned documents as e-mail attachments via SMTP, with a download-link fallback for oversized scans |
|
|
Save to local or network (SMB/CIFS) folders, with DFS support |
|
|
Upload via FTP/FTPS |
|
|
Upload to on-premises SharePoint document libraries using Windows authentication |
|
|
Upload to Microsoft 365 SharePoint via Microsoft Graph (OAuth 2.0) |
|
|
Upload to Google Drive via OAuth 2.0 |
|
|
Upload to Dropbox cloud storage (OAuth 2.0) |
|
|
Upload to Microsoft OneDrive (Personal or Business) via Microsoft Graph (OAuth 2.0) |
|
|
Upload to Box cloud storage (OAuth 2.0) |
|
|
Upload to any WebDAV-compatible server (Nextcloud, ownCloud, NAS devices) |
|
|
Upload to S3-compatible object storage (Amazon S3, Wasabi, MinIO) |
|
|
Store scans in OptimiDoc for retrieval from the web interface, with optional e-mail notification |
|
|
Execute a custom script or application for custom processing and delivery |
Destination Categories
Local and Network Storage
|
Type |
Protocol |
Authentication |
|---|---|---|
|
Folder |
SMB/CIFS |
Windows credentials (optional) |
|
FTP |
FTP/FTPS |
Username/password |
|
WebDAV |
HTTP/HTTPS |
Username/password |
|
SharePoint (on-premises) |
HTTP/HTTPS |
Windows (NTLM) |
Microsoft 365 Cloud
|
Type |
Service |
Authentication |
|---|---|---|
|
SharePoint Online |
Microsoft 365 SharePoint |
Azure AD OAuth 2.0 (Microsoft Graph) |
|
OneDrive |
Microsoft OneDrive |
Azure AD OAuth 2.0 (Microsoft Graph) |
Other Cloud Services
|
Type |
Service |
Authentication |
|---|---|---|
|
Google Drive |
Google Workspace |
OAuth 2.0 |
|
Dropbox |
Dropbox |
OAuth 2.0 (built-in app) |
|
Box |
Box |
OAuth 2.0 (built-in app) |
|
S3-Wasabi |
S3-compatible storage |
Access key / Secret key |
Internal and Custom
|
Type |
Service |
Authentication |
|---|---|---|
|
OptimiDoc |
Internal OptimiDoc storage |
N/A |
|
|
SMTP mail server |
Login/password or OAuth 2.0 |
|
Script |
Custom integration |
N/A |
Related Articles
-
Scan Templates -- Overview of scan template configuration
-
Output Options -- Filename patterns, formats, and destination assignment
-
Scan Parameters -- Parameter types for conditional routing