🔗 Before you begin: To use this feature, you must first connect Salesforce as a Data Fabric integration.
See: [How to Set Up the Salesforce Integration as a Data Source]
Direct File Delivery for Salesforce allows you to write files directly to Salesforce records as part of the Deliver Data step in Streamline.
Files generated or collected during workflow execution — including Form uploads, generated Documents, or signed files — can be delivered to Salesforce as:
- Salesforce Files (ContentVersion)
- Legacy Attachments (Attachment object)
This enables complete round-trip document management within Salesforce without requiring separate iPaaS integrations or external file storage.
Who Has Access?
This feature is available to all Streamline users who have:
- A configured Salesforce Data Fabric integration
- Proper Salesforce permissions through the connected user
No additional licensing tier or feature add-on is required.
Feature Capabilities
Supported Delivery Patterns
Direct File Delivery supports two delivery methods:
1. File-to-Entity (Automatic Detection)
When using supported Salesforce objects:
- Streamline automatically detects if the entity supports file associations
- A Files section appears in the Deliver Data configuration
- Files are mapped directly from workflow steps
- Streamline creates ContentVersion records automatically
- Files are linked using FirstPublishLocationId
- No manual configuration of file-related entities is required
- File type is automatically detected and the correct extension is appended
Note: File-to-Entity supports Salesforce Files (ContentVersion) only. Legacy Attachments require File-to-Field mapping.
2. File-to-Field (Manual Mapping)
For more granular control or legacy Attachment use:
- Add ContentVersion or Attachment as related entities in your dataset
- File-type fields appear in the standard mapping interface
- Map files to specific fields such as:
- VersionData
- Body
- Provides explicit control over metadata and field mapping
Required when:
- Using legacy Attachments
- Customizing file metadata fields
Supported Salesforce Storage Types
| Storage Type | Salesforce Object | Key Field | Size Limit | Detection |
|---|---|---|---|---|
| Salesforce Files (Modern) | ContentVersion | VersionData (Base64) | 2 GB | Auto-detected or manual |
| Legacy Attachments | Attachment | Body (Base64) | 25 MB | Manual only |
Supported File Sources
Files can originate from any workflow step that produces files:
- Form step – File upload fields
- Document step – Generated PDFs and templates
- Sign step – Signed and executed documents
Supported File Formats
All file formats are supported, including:
- DOCX, DOC
- XLSX, XLS
- PNG, JPEG, GIF, TIFF
- Any file type produced within Streamline
File Metadata Mapping
The following file properties are available for mapping:
Property |
Description |
Mapping Target |
Required |
|---|---|---|---|
File Content |
Binary file data |
VersionData (Files) or Body (Attachments) |
Yes |
File Name |
Custom file name (extension auto-appended) |
Title (Files) or Name (Attachments) |
Yes |
File Extension |
File extension extracted from filename (includes the dot) |
Available for metadata fields |
Optional — file type is auto-detected |
Content Type |
MIME type (e.g., |
Required for Attachment, optional for ContentVersion |
Varies |
Dynamic File Naming
File names support dynamic naming using workflow tokens.
Example:
{{Form.FirstName}}_{{Form.LastName}}_ContractThe correct file extension is automatically appended based on file type. You do not need to manually include the extension unless referencing it elsewhere.
Multiple Files Per Record
- Multiple files can be mapped to a single Salesforce record
- Each file requires its own mapping row
- Each row supports one file only
Encoding
Base64 encoding is handled automatically by Streamline. No manual encoding is required.
Transaction Behavior
File delivery behaviour varies depending on the mapping method:
| Delivery Pattern | Transaction Behavior | Rollback on File Failure |
|---|---|---|
| File-to-Entity | Separate transaction | Parent record not rolled back |
| File-to-Field (Attachment) | Same transaction | Entire record rolled back |
| File-to-Field (ContentVersion) | Separate transaction | Parent not rolled back |
Feature Considerations & Limitations
File Size Limits
- Salesforce Files: 2 GB maximum
- Legacy Attachments: 25 MB maximum
Files exceeding limits will fail with clear error messages.
Synchronous Upload
File uploads are synchronous:
- Workflow waits for upload to complete
- No asynchronous option
- Large files may increase execution time
Very Large File Timeout Risk
For files approaching 2 GB:
- Upload may exceed internal processing timeout
- Workflow session may fail even if file upload continues
- Retry may create duplicates
Recommendation: Monitor large uploads carefully and verify Salesforce before retrying.
One File Per Mapping Row
Each mapping row supports only one file. Add additional rows for multiple files.
Legacy Attachments Not Auto-Detected
Attachment object must be manually added for use. Salesforce Files (ContentVersion) are recommended unless legacy attachments are required.
No String-to-File Conversion
- Cannot map String (Base64) to File fields
- Cannot map File to String fields
- Files must originate from File-producing workflow steps
Salesforce API Constraints
- REST API requires Base64 payloads
- Multipart streaming not supported
- Large files may upload slowly
Compliance & Security
Direct File Delivery follows Streamline’s standard security practices:
- Uses the same Salesforce OAuth credentials
- Files transmitted via secure HTTPS
- Access governed by Salesforce sharing rules
Delivered files inherit Salesforce’s:
- Sharing rules
- Retention policies
- Access controls
Troubleshooting
File Delivery Fails with Size Error
- Verify file size limits
- Compress file if possible
- Monitor workflow execution time
File Not Visible in Salesforce
- Confirm correct record ID
- Verify ContentDocumentLink or ParentId
- Check Salesforce user permissions
Files Section Not Appearing
- Ensure target object supports file associations
- For Attachments, use File-to-Field mapping
Incorrect File Name or Metadata
- Verify token expressions resolve properly
- Confirm file name mapping
- Extension is auto-appended
Workflow Failed but File Exists
- Very large files may exceed timeout
- Verify Salesforce state before retrying
- Retrying may create duplicate files
Parent Record Created but File Missing
- File uploads are separate transactions
- Review workflow logs for file-specific errors
- Re-run workflow or upload manually
Comments
0 comments
Article is closed for comments.