Home | Connectors | S-Drive | S-Drive - Ziflow Integration and Automation
When a Salesforce opportunity, campaign, or case reaches a defined stage, S-Drive can trigger the creation of a proofing request in Ziflow with the related brief, supporting files, and record metadata. This gives creative teams immediate context and ensures review starts with the correct source materials.
After a proof is approved in Ziflow, the final approved file, version history, and approval status can be pushed back into S-Drive and attached to the relevant Salesforce record. This creates a single operational view of the approved asset alongside the customer, campaign, or request it supports.
S-Drive can collect required intake documents from Salesforce users or external stakeholders, such as brand guidelines, legal disclaimers, product sheets, or regulated content references, and then pass them to Ziflow as supporting materials for review. This is especially useful for industries that require compliance checks before publication.
Ziflow review outcomes, including comments, approval decisions, and outstanding revision requests, can be synchronized back to Salesforce through S-Drive-linked records. Sales, marketing, legal, and operations teams can then monitor creative progress without leaving Salesforce.
Marketing teams often revise campaign assets multiple times before launch. S-Drive can store each version in Salesforce, while Ziflow manages the proofing cycle for each revision. Once a version is approved, the final file and approval record can be stored back in S-Drive, preserving the full lifecycle of the asset.
For regulated industries, S-Drive can route contracts, disclosures, or product claims from Salesforce into Ziflow for legal, compliance, and brand review. Once approved, the signed-off version is returned to S-Drive and linked to the originating Salesforce case, opportunity, or account.
Account teams can use Salesforce to manage customer-specific deliverables such as proposals, co-branded materials, or localized assets. S-Drive stores the customer files and sends them to Ziflow for review, while final approvals and published versions are returned to the Salesforce account record for easy retrieval.
If a proof is rejected in Ziflow, the rejection reason and required changes can be sent back to S-Drive and linked to the Salesforce task or request. This can automatically create a follow-up action for the responsible team member, ensuring revisions are tracked and completed without manual follow-up.