# Multi-Source Triggers

Multi-Source Triggers automatically detect file additions or updates across Salesforce, connected storage systems, and CloudFiles components, generating CloudFiles Events that trigger AI-powered processing.

> Kind: Guide · Updated: Jul 4, 2026

Files today come from everywhere, Salesforce manual uploads, External Cloud Storages (SharePoint, Google Drive etc.), inbound emails, or other third party integrations. Without a unified system to detect and process these files, organizations end up creating fragmented workflows and missing automation opportunities.

Multi-Source Triggers automatically detect file additions or updates across Salesforce, connected storage systems, and CloudFiles components. Each event, whether it's a new upload, file update, or folder creation, generates a CloudFiles Event that can be used to trigger AI-powered processing or any other downstream workflow.

Once configured, CloudFiles ensures every document is captured, analyzed, and routed, no matter its source.

> Refer to Intercepting CloudFiles Events article for more information.

Across industries, multi-source triggers simplify document workflows by automating AI processing from multiple entry points. In insurance, claim forms uploaded via Email-to-Case or SharePoint folders are automatically processed by Document AI to extract key details. In manufacturing, when a supplier uploads an invoice to OneDrive, AI processing captures the invoice data and updates Salesforce records.

CloudFiles can initiate processing from multiple channels. Below are all supported trigger categories along with their corresponding CloudFiles Event Types and descriptions.

## Salesforce-Based Triggers

CloudFiles integrates natively with Salesforce, enabling AI processing when key record or file-related events occur. You can automate processing when a file is attached, a record changes, or another Salesforce-integrated app uploads a document.

Common Trigger Scenarios

- A file is attached to a Salesforce record (e.g., Case, Opportunity, Lead).
- A record is created or updated, triggering a new processing workflow.

When key fields like status or stage change, Cloudfiles Document AI can automatically process files, and initiate the next step in the workflow.

- A file is received via Email-to-Case or other native integrations.                 Attachments coming in through inbound emails or Salesforce-connected channels are auto-ingested for processing.
- An external app pushes files into Salesforce.                                                              Files uploaded through third-party platforms can be automatically processed once they reach Salesforce.

Relevant CloudFiles Event Types

| Event Type | Description |
|---|---|
| salesforce-file-attached | Triggered when a file is uploaded to Salesforce native storage (e.g., via Files or Notes & Attachments). |

## CloudFiles Document Management

CloudFiles Document Management integrates seamlessly with external storage systems such as Google Drive, SharePoint, OneDrive, and AWS S3, as well as with CloudFiles Components (widgets, Datarooms, and Lightning Components) embedded within Salesforce.

Files that are uploaded, modified, deleted, or accessed through any connected source can automatically trigger AI-driven workflows for document classification, data extraction, and downstream automation.

Common Trigger Scenarios

- New file upload: Files added via external storage, CloudFiles widgets, or Dataroom File Requests automatically initiate Document AI processing.
- File modification or replacement: Updated files trigger re-processing or metadata synchronization in Salesforce.
- Folder creation: Folders created via Flow or CloudFiles actions can initiate automated organization or compliance workflows.
- File or folder cloning: Deletions or cloning operations can trigger cleanup or downstream process updates.
- Merged document split: Automatically splits combined documents into individual records through Document AI.

Relevant CloudFiles Event Types

| Event Type | Description |
|---|---|
| resource-attached | Triggered whenever a file or folder in external storage is attached to a Salesforce record. |
| content-version-created | Triggered when a Salesforce File (Content Document) is created from an external storage file. |
| resource-updated | Triggered when metadata of a file or folder is updated from Salesforce. |
| file-uploaded | Triggered when a file is uploaded to external storage via the CloudFiles widget in Salesforce. |
| resource-cloned | Generated for each successful external resource cloning operation, enabling chained or downstream processes. |
| file-received | Triggered when a file is uploaded via the File Request module in a CloudFiles Dataroom. |
| document-split | Triggered after a merged file is automatically split into separate documents by Document AI |

> There are additional events beyond those mentioned here, which can be used as per your specific use case. Refer to the All Event Types article to learn more.

## Summary

Multi-Source Triggers in CloudFiles automatically detect and respond to file activities such as uploads, updates, or folder creations across Salesforce, external storage systems (like SharePoint, Google Drive, etc;), inbound emails, and CloudFiles components. Each activity generates a CloudFiles Event that can initiate AI-driven workflows for document classification, data extraction, and automation. This ensures every file, regardless of its origin, is intelligently captured, processed, and routed within your workflows, reducing manual effort and fragmentation across systems.