Flow action categories

  • Doc Management Flow Actions: Automate file and folder operations across external storage platforms — creating, copying, moving and deleting resources, managing record attachments, retrieving metadata, updating permissions, and syncing files between external storage and Salesforce.
  • Doc Sharing Flow Actions: Automate file and content sharing workflows — creating and managing datarooms, generating shareable links, handling file requests, sharing resources with Experience Cloud users, and updating link security settings.
  • Doc Generation Flow Actions: Automate document generation directly within Flow Builder — generating single or multiple documents asynchronously or synchronously, and combining multiple files into a single document in real time.
  • Doc AI Flow Actions: AI-powered document processing within Flow Builder — creating datasets, extracting structured data to create or update records, processing and querying documents using natural-language prompts, and splitting merged PDFs into individual documents.
  • Misc Flow Actions: Assign and remove CloudFiles product licenses, add delays to flow executions, and retrieve CloudFiles event details for platform event-triggered flows.
  • Screen Flow Elements: CloudFiles elements for Salesforce screen flows — the internal record widget, the Experience Cloud widget, and the CloudFiles uploader.

Adding actions in flows

Create a standard Salesforce flow with any type of trigger conditions. Then add an element and choose Actions. If CloudFiles is correctly installed and connected, you can find the actions under the CloudFiles category.

Note

If you use a record triggered flow, make sure you run this action on an asynchronous path as shown below.

Action limits

Each flow action may include one or more API calls made to the CloudFiles server. Depending on the action type, this contributes either one or more action executions toward the automation action limits defined for each tier.

You can use the following list as a reference to understand how your flow actions will contribute towards the automation action limits.

Count of 1

These actions contribute a count of 1 each time they are executed: Create Folder, Create Attachment, Get Attachments, Delete Attachments, Create Dataroom, Create File Request, Add to Dataroom, Create Link, Get Event Details, Get Connected Folder, Get Files Connect Resource ID, Create Files Connect Files, Update Permissions, Get Folder Contents, Get Resource Property, Set Resource Property, Get Salesforce Files.

Variable count

These actions contribute a variable count to the limit each time they are executed: Copy Salesforce Files, Copy Resources, Move Resources. The count contributed depends on the number of resources passed into the action (for example, if 2 files are passed into the Copy Resources action, this contributes a count of 2 toward the limit).

Not counted

These actions are not counted towards the limit since they are not used in everyday flows: Create Folder Async and other async actions used for migration purposes.