Process External Files

overview in this tutorial, we will guide you on how to process external files for document ai cloudfiles supports ai on various external storages such as sharepoint, google drive, aws s3 etc processing the files is a mandatory step that must be done before ai queries can be executed on a file processing makes the file ready for cloudfiles ai you will need to create 2 separate flows the first flow will trigger when the upload is done and will send the uploaded file to ai for processing the second flow will trigger when the document has finished processing and can now be queried process new document flow this flow sends any new file uploads for processing processing is an asynchronous operation and may take some time to complete document processing complete flow this flow executes when the document has been processed this is the flow in which you will actually add the query & response logic read the sections below carefully to setup these 2 flows pre requisites ensure the following before starting ensure neccessary setup is done for docid 3gglz90lgx5zfwkrgm7ra cloudfiles document ai docid\ rfxciqrbejmpsmbczexam and docid\ amnhmxwixyngnaxerbkwd are complete you have an active subscription or trial of cloudfiles document ai the cloudfiles event mode setting is set to custom object process document flow this flow is triggered whenever a new file is uploaded in an external storage through the cloudfiles lwc it processes each uploaded file using docid 31ujx1ligtkwfkjuanbzt in the context of the triggering record successful file processing publishes a docid\ xrr pnbpocwwcmyg6qgk9 event, triggering the document processing complete flow that is covered in the next section check the sub sections below for details on each of these steps create record triggered flow create a new record triggered flow with the triggering object type set as cldfs cloudfilesevent c additionally set some filter conditions this ensures that the flow is only triggered for the correct type of events e g using the below conditions, we will only trigger the flow when a new file is uploaded on contact records type ( cldfs type c ) = file uploaded include a run asynchronously path to access an external system after the original transaction for the triggering record is successfully committed here's how the trigger conditions would look like get event details now that we have trigger setup, we will get more details related to the event we will use the get event details action for this within in the run asynchronously path, add the get event details action under "set input values", toggle event (custom object) and select triggering cldfs cloudfilesevent c ( {!$record} ) process uploaded file in order to actually process the file, we simply use the process document flow action as shown below this action takes in the following parameters library select outputs from get triggering event details > uploaded file details > library ( {!get triggering event details fileuploaded library} ) drive id select outputs from get triggering event details > uploaded file details > driveid ( {!get triggering event details fileuploaded driveid} ) file id select outputs from get triggering event details > uploaded file details > id ( {!get triggering event details fileuploaded id} ) context select outputs from get triggering event details > uploaded file details > recordid ( {!get triggering event details fileuploaded recordid} ) optionally, set instructions with special processing guidelines document processing complete flow this flow is triggered when the document we sent for processing in the flow above has finished processing we will use the docid\ xrr pnbpocwwcmyg6qgk9 event along with a record triggered flow to intercept this we will then get the event details that will give us the triggering record and the processed document id that can be used later to perform ai queries on the document create record triggered flow create a new record triggered flow with the triggering object type set as cldfs cloudfilesevent c additionally set some filter conditions this ensures that the flow is only triggered for the correct type of events e g using the below conditions, we will only trigger the flow when a new file is uploaded on contact records type ( cldfs type c ) = document processed include a run asynchronously path to access an external system after the original transaction for the triggering record is successfully committed here's how the trigger conditions would look like get event details now that we have trigger setup, we will get more details related to the event we will use the get event details action for this within in the run asynchronously path, add the get event details action under "set input values", toggle event (custom object) and select triggering cldfs cloudfilesevent c ( {!$record} ) useful event information now that we have the event details of the document processed event, we can use this to get 2 useful pieces of information processed document id this will be used as an input to the query document action that has used in various other tutorials on docid\ k89awfijxxjssysaajwcr context this is important to retrieve the record id or other important metadata that you want to pass when processing the document check the process each file section above to understand what is retrieved in the context output file details of the processed file specified in the input, which helps identify the file post processing what next? in this tutorial, we have only explained how to process a salesforce file so that it is ready for ai queries for actually understanding how automated queries can be performed and how the responses can be used to enrich salesforce data, check the other tutorials mentioned in the docid\ k89awfijxxjssysaajwcr article