Product Updates

Complete the Loop: Write Files Directly to Salesforce from Your Workflows

Josh Katinger

Principal Product Manager

Write files to Salesforce records as part of your workflow

With Direct File Delivery for Salesforce, Intellistack Streamline’s Data Fabric —which connects to your systems without copying or storing data— handles files the same way it handles structured data — directly, securely, and natively within your workflow.

Forms collect file uploads. Documents generate PDFs. Signatures produce signed contracts. Now, all of these can land directly on the Salesforce records where they belong.

From workflow to Salesforce record in one step

Direct File Delivery lets you map files from any Streamline workflow step directly into Salesforce records. A signed contract lands on the Opportunity. An uploaded W-9 attaches to the Vendor record. A generated PDF lives alongside the Case it documents.

One workflow. One destination. Complete data integrity.

Two ways to deliver files

File-to-Entity (the easy path)

The platform automatically detects when a Salesforce entity supports file associations and surfaces a dedicated "Files" section in your Deliver Data configuration. Map your files — the platform creates the ContentVersion records and links them to the parent entity. No knowledge of Salesforce's file architecture required.

‍File-to-Field (full control)

For builders who need explicit control, you can manually add file-related entities (ContentVersion, Attachment) to your dataset and map files to specific fields. This approach gives you direct access to metadata fields and lets you configure exactly how files are stored and named.

What you can deliver

Source	Examples
Form uploads	W-9s, receipts, photos, supporting documents
Generated documents	PDFs from Document step, merged templates
Signed documents	Executed contracts, acknowledged agreements

All file formats are supported — PDF, DOCX, PNG, JPEG, whatever your workflow produces. The platform handles Base64 encoding automatically; you just map the file.

Salesforce file storage, explained

Salesforce has two file storage mechanisms. Direct File Delivery supports both:

Storage Type	Object	Size Limit	When to Use
Salesforce Files (modern)	ContentVersion	2 GB	Default recommendation. Auto-detected by File-to-Entity.
Legacy Attachments	Attachment	25 MB	For orgs using Notes & Attachments. Available via File-to-Field.

If you're not sure which to use, go with Salesforce Files — it's the modern standard and supports larger files.

File metadata at your fingertips

When mapping files, the platform exposes key properties you can use:

File Content — The actual file data (automatically encoded)
File Name — Supports dynamic naming using workflow data
File Extension — Available for advanced use cases (optional — file type is auto-detected)
Content Type — MIME type (application/pdf, image/png, etc.)

The platform automatically detects the file type and appends the correct extension, so you can focus on naming your files meaningfully (e.g., {{FirstName}}_{{LastName}}_Contract) without worrying about extensions.

Built for reliability

Clear size enforcement — If a file exceeds the target's limit (2 GB for Files, 25 MB for Attachments), the delivery fails with a clear error before creating partial records.
Retry-safe — If a delivery is retried, no duplicate files are created.
Same security model — File delivery uses the same Salesforce credentials and access controls as your data integrations.

Who this is for

Direct File Delivery for Salesforce is built for organizations where Salesforce is the system of record and workflows generate documents that belong with the data they reference: