In this tutorial, we will see how CloudFiles can be used with Salesforce flow automations to create a KYC upload checker. While this tutorial is similar in functionality to AI-Powered KYC Upload Checker, instead of performing multiple Query Document calls, we will perform a single call for multiple actions using the Query Document (Batch) action.

Each time a file is uploaded into Salesforce or external storage, the following actions will occur :

In order to setup this automation, you first need to have some pre-requisites. After this you can start setting up some query automations and updates to achieve your use-case. Check the sections below for more information. In the image below, we have demonstrated this in action.

Before starting with this tutorial, you need to ensure that CloudFiles Document AI is properly installed & configured in your system. Additionally, you also need to create some initial automations to process the files before you can query them. Check the 2 sections below carefully -

Ensure the following before starting:

There are 2 flows you will need to setup to process the uploaded files. The first flow is triggered when the document is uploaded into Salesforce or external storage. This flow sends the file to AI for processing. This might take a few seconds. Once the AI is done with processing, the second flow will trigger which will contain the processed document. You can then run queries on this processed document.

All information related to setting up these flows is given in the AI Flows - Initial Setup Guide article. Please go through this article carefully to set up these flows.

Once your flow setup is complete, your flows should look like the following-

Now that you have the initial automation setup, we can take the document processed flow and extend it to query the document and update the required fields. In this section, we show how to query the processed document, check the results and perform the necessary updates.

In order to classify the document, we will simply use the Query Document flow action along with a natural language prompt. This action taken in a processed document ID and a text query as input. The processed document ID is available as output of the Get Event Details action. Here are the full inputs used in the image below.

Processed Document Id = Outputs from Get Event Details : Get Processed Event Details > Document Processed > ProcessedDocumentId

Query = Classify the file as either a driving license or a passport. If the file does not match either of these types, classify it as other. Based on the classification, give the output as one of the following - Driving License, Passport, or Other.

Now that our documents are classified, we can use the output of the 'Query Document' action to create 2 branches in our flow. In each of the branches, we will ask document specific questions to extract relevant information. We will use the Query Document (Batch) action to perform all queries in a single call.

In order to batch queries, first create an apex-defined variable of class cldfs__QueryDocumentPrompt for each of the queries you need to run. This means you will need to create multiple such variables. Here is an example of one such variable.

Now using an assignment flow action, assign the 'id' & 'query' fields to your created variable as shown below. Here id is a text identifier that we will use later while looping over the batched results. Query is the natural language prompt you wish to ask AI.

Repeat this for the queries you need to run. As you can see below, we have created and assigned multiple such variables, each with a different id & query. Here are some example queries we used :



Now that you have constructed the variables, we will combine them into an apex-defined collection variable of class cldfs_QueryDocumentPrompt.

The creation of this collection variable has been shown in the image below-

Once created, you can simply use an assignment operator to add the above variables into this collection. This has been shown below-

The previous consolidates all constructed queries into a single collection, preparing them for batch execution using Query Document (Batch). In this step, we will actually use this action along with the collection variable from previous step to execute these queries. This action takes in 2 inputs -

The final action with the inputs is shown below -

This step executes all data extraction queries simultaneously, optimizing performance and ensuring efficient processing.

The batch action above provides the results in a batched manner as well. We need to loop through these results in order to update them in our Salesforce record. We further need to filter the results into branches in order to update them in the correct salesforce properties. This step allows the flow to individually handle each query result, thus giving more control.

The image below shows how the loop has been setup. Set the Collection Variable to Outputs from Execute Passport Queries > Prompts.

Once you have setup the loop, you can check the loop item's 'id' field in order to create the branches. These are the same IDs that we provided above while creating the Query variables. The image below shows an example branch-

Now that we have branches created to handle the response of each of the individual queries sent, we can easily update our record fields. While we can simply add the Update record action into these branches, this will trigger multiple record updates for the same record in a short time.

Since it is a good practice to perform less number of record update calls, we will use a simple trick. We will create some empty text variables for each of the responses, and store the result from the response array into these variables. You can simply create a text variable assign the looped item's 'result' as shown in the screenshot below-

Now that we have various variables for our responses, we can use a singular Update Record method to update the fields with these values. This has been shown below-

That's it. Your flow is now configured to run multiple queries in a batch and save the responses in record fields.

Now that everything is set up, you can test your flows. When a Passport or Driver's License is uploaded as Salesforce Files onto a Contact record, the mapped fields should be updated automatically.

Congratulations! You've successfully created an AI-powered KYC Documents checker using CloudFiles AI & Salesforce flow.

While this tutorial provides a simple and specific use case for processing Salesforce Files, the same logic can be extended to various scenarios such as:

Explore these use cases to streamline your document management and Salesforce data updates, enhancing your organization's efficiency and accuracy.