Process Document using AI

introduction the cloudfiles process document using ai flow action is a foundational step for working with documents in cloudfiles document ai before you can query a document, it must be processed first in other words, just as you would upload a file to an ai system to later ask questions about it, cloudfiles requires this initial processing to make the document accessible for querying the process document using ai action handles this, preparing the document for subsequent queries this processing is an essential prerequisite for any workflow that involves further cloudfiles document ai actions (for example, query document docid\ dm3eh gzaocyoqd5y0r8d ) analyzing document content or extracting specific details, such as identifying document type or pulling specific values for other fields what this action does this action runs asynchronously, meaning it does not provide immediate output the process document using ai action converts documents, such as images or pdfs, into a digitized, queryable format that cloudfiles can interpret instead of returning output directly, it publishes a document processed docid\ xrr pnbpocwwcmyg6qgk9 event once the processing is complete this event details include processeddocumentid (a unique cloudfiles identifier), which is essential for further cloudfiles document ai actions, enabling you to query and interact with the document’s contents in subsequent flows consider a scenario where you need to process kyc documents attached to contact records in salesforce, such as passports or national identity certificates you may want to automatically identify the document type (e g , “is this document a passport?”) and, if it is, query additional information such as the address or nationality to populate fields on the contact record to enable this process, you would create a flow that triggers each time a document is attached to a contact record and uses the process document using ai action to make the document ready for querying set up another flow triggered by the document processed event, which references processeddocumentid (a unique cloudfiles identifier) and information to identify its origin (such as the specific contact record and processed file details) and use other cloudfiles document ai actions to query and gather further information from the file this setup allows you to automate document classification and content extraction workflows effectively input parameters in your flow builder, search for the element named " cloudfiles process document using ai " you can find this action in the cloudfiles category when you click on the "action" element in the "add element" box select the action to insert it into the flow, and then configure the input parameters to process a salesforce file in order to specify a salesforce file to be processed, input paramters as library salesforce fileid the contentdocumentid of the salesforce file to be processed you can get the contentdocumentid of the salesforce file from other standard salesforce elements like "get records" or standard screen flow "upload files" component or from details of cloudfiles events like salesforce file attached docid\ cnswhxyiaabekamvbfxon you can only process a salesforce file in contentdocument https //developer salesforce com/docs/atlas en us object reference meta/object reference/sforce api objects contentdocument htm format you cannot process an attachment i e classic salesforce file format it is mandatory to input both library and fileid to specify a salesforce file to process an external storage file if you are using cloudfiles document managemnt pacakage as well, then you can process a file in connected external storage as well in order to specify an external storage file to be processed, input paramters as library the library parameter is the external storage type you are using possible values are sharepoint , google (for google drive), onedrive , dropbox , box , azure , cloudfiles (for aws s3) drive id the if of the drive where the document resides this is important for google drive & sharepoint libraries only the drive id is a unique identifier for a storage location in both sharepoint and google drive in sharepoint, it represents a document library within a site, while in google drive, it identifies a user's drive or shared drive fileid the unique identifier (resource id) of the file that is to be processed based on the use case, you can get these parameters from details of other cloudfiles events like file uploaded docid\ p yy1ryebu5ecnctf0jhd or file received docid\ napychk2t4mc8kkvguxig etc context an optional identifier to track the source of the event or any other intended/necessary details this shall be available in corresponding output i e in the corresponding document processed docid\ xrr pnbpocwwcmyg6qgk9 event details the context parameter is particularly helpful if this action is used in multiple flows for example, if you’re processing documents attached to contact records, you can set the contact’s record id as the context when events are published, this context value will help you track the origin of each event by showing the associated contact record instructions (optional) the instructions input parameter allows you to guide cloudfiles document ai with specific context or expectations when processing a file providing clear, relevant instructions can significantly improve processing speed, classification accuracy, and downstream data extraction why use instructions? this is especially useful when dealing with complex, merged, or multi section documents where a general understanding may not be enough for precise parsing improves ai interpretation by narrowing the context helps ai focus on document structure or content types reduces ambiguity in document classification or segmentation optimizes performance by pre defining what the ai should look for example processing purchase orders with order line items you are provided with a purchase order document that includes summary information and detailed line items your task is to accurately extract structured data from the document the common components you should recognize and extract include po number – a unique identifier for the purchase order, often found at the top or in a header section po date – the date the order was created or issued vendor information – the name, address, and contact details of the supplier/vendor buyer information – the name, address, and contact details of the purchasing organization or department shipping/billing address – the address where the goods should be delivered or address used for invoice and payment processing currency – the currency in which the order is being placed (e g , usd, eur) order line items – for each line item, extract the following item description, item code / sku, quantity, unit price, total line amount (quantity × unit price), uom (unit of measure),grand total – the final total payable amount payment terms – specified terms for invoice payment (e g , net 30, advance payment) delivery terms / incoterms – if provided, terms related to delivery responsibility po notes / special instructions – any additional notes, disclaimers, or delivery instructions included in the document ensure accurate mapping of each order line item as a separate object if needed for downstream automation (e g , creating order line items in salesforce) handle tables and lists carefully, preserving row integrity output parameters the apex action does not return anything as an output in the flow it is used but for every file processed a document processed docid\ xrr pnbpocwwcmyg6qgk9 event is published this event signals the completion of file processing and can be used to trigger platform event flows to perform post processing actions such as query document docid\ dm3eh gzaocyoqd5y0r8d or query document (batch) docid\ ok1o1lpb07zvaclnrbgvu if the action fails due to some reason, an error event event will be triggered and this event can be used in a decision element to diagnose and handle the error