Flow Actions
list of actions this collection consists of all salesforce flow actions and component related articles that are provided out of the box by cloudfiles salesforce integration doc management flow actions docid\ odvyhv6yjk4bm1k055doe this section covers all document management flow actions available in salesforce, enabling automation of file and folder operations across external storage platforms actions include 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 docid 0up2fhybvecjchcoofygg this section covers all document sharing flow actions in salesforce for automating file and content sharing workflows it includes actions for 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 docid\ nv27oftdk5ukedfzqpbpq this section covers all document generation flow actions in salesforce, enabling automation of document generation directly within flow builder it includes actions for generating single or multiple documents asynchronously or synchronously, and combining multiple files into a single document in real time doc ai flow actions docid\ qkkhj1ixbvv6uxb w6dtq this section covers all document ai flow actions in salesforce, enabling ai powered document processing within flow builder it includes actions for creating datasets from multiple files, extracting structured data to create or update salesforce records, processing and querying documents using natural language prompts, running multiple queries in a single action, and splitting merged pdfs into individual documents misc flow actions docid\ axhgtzr v6erygxn3oxbj this section covers miscellaneous flow actions in salesforce, including automating the assignment and removal of cloudfiles product licenses, adding delays to flow executions, and retrieving cloudfiles event details for use in platform event triggered flows screen flow elements docid\ p7pzn4vlvxczunzozfhjn this section provides an overview of the cloudfiles elements available for salesforce screen flows, including the internal record widget for displaying files and folders linked to salesforce records for internal users, the experience cloud widget for allowing external users to securely access, upload, and manage files, and the cloudfiles uploader for uploading files directly to external storage platforms adding actions in flows create a standard salesforce flow you can choose to have any type of trigger conditions here then, add an element and choose actions if you have cloudfiles correctly installed and connected, you can find the create folder action in the cloudfiles category 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 above may include one or more api calls made to the cloudfiles server depending on the type of action, this contributes either one or more action executions these executions are counted towards the automation action limits defined for each tier https //help cloudfiles io/webapp/document automations# cqbj you can use the following list as a reference to understand how your flow actions will contribute towards the automation action limits 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 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 e g if 2 files are passed into the copy resources action, this will contribute a count of 2 towards the limit these actions are not counted towards the limit since they are not used in everyday flows create folder async, other async actions used for migration purposes