In this tutorial, we’ll guide you on creating a KYC Upload Checker for an Account object using CloudFiles Document AI and Salesforce Integration. We will leverage CloudFiles AI in conjunction with Salesforce flow to create this functionality. This checker will automatically scan uploaded passports and driving licenses, extract key details, and update corresponding fields in Salesforce, significantly enhancing the efficiency and accuracy of your KYC processes.

By the end of this tutorial, you can expect to -

The GIF below shows the expected output. If you have a basic grasp of these concepts, you can expect to finish the tutorial in under 10 minutes.

Before you start with the set-up, please ensure these steps are completed.

CloudFiles is available on the Salesforce AppExchange and can be installed using the standard app installation process. Check out Installation Guide to know more.

To add the CloudFiles widget to the Account record in Salesforce, first, navigate to the Account page and click on the "Edit Page" button. Once in the Lightning Builder, insert a new tab and drag and drop the "CloudFiles" widget onto the page. Save the changes and exit the builder. Refresh the Salesforce record page, and the widget should now be visible, allowing easy access to view files and folders within Salesforce.

Refer to the image below to have a visual understanding of these custom fields -

To create the AI-powered KYC Upload Checker, we set up a platform-triggered flow that activates upon receiving a 'CloudFiles Event' message. We ensured the uploaded file is associated with the Salesforce Account object and then extracted KYC document details using specified parameters like Context, Drive Id, File Id, and Library. After confirming document processing, we applied CloudFiles AI to classify the document as a driving license or passport and extracted relevant details. Finally, we updated the Salesforce Account object with the extracted information. This is the final flow that has been created.

These steps have been discussed below in detail -

We will create a platform-triggered flow that will fire when a ‘CloudFiles Event’ message is received. Refer to the GIF below for a visual understanding of this step -

‘CloudFiles event’ messages can be generated for various events, we will first filter out the messages only for the event when a file is uploaded to an Account Object. We will proceed to retrieve & process the uploaded document.

We will add a decision outcome to filter out events where the file is uploaded to the Salesforce Account object. Then, we will use two CloudFiles actions to first retrieve the account details and then the file details for further processing.

We will add a decision element to ensure that the file to be processed is uploaded to the Salesforce Account object. It will ask you to fill in certain parameters. We will add 2 resources as given below -

This is how the Outcome Detail looks like -

Refer to the gif below for a visual understanding of this step -

In order to get the Account ID of the account for which the file upload has happened, we will use the CloudFiles action - “Get Events Details’.

To retrieve event details, we'll use the 'Get Event Details' action, which provides various information about the event, including the content version and uploaded file details. Outputs from this action will be used in the next action. In the ‘Get Event Details’ action, put {!$Record} as an event.

Refer to the GIF below to have a visual understanding of this step -

Once we have received the event details, we will use the 'Process Document' action to obtain the uploaded file details for further processing. To do this, you need to fill in the following parameters

This is how the action looks like -

Refer to the GIF below to have a visual understanding of this action -

Once the file is processed, we will proceed to ask a series of prompts to obtain the required details from the file. First, we will add a second decision outcome to fetch the previously processed files. Then, we will retrieve all the file details using the ‘Get Event Details’ action. Once we have the required details, we will ask a series of prompts to the document through the ‘Query Document’ action, which will classify the document as a specific KYC type. The following steps outline this process in detail -

We will add a ‘File Processed’ outcome in the decision element to fetch the previously processed files for further processing. Fill in the parameters as given below -

{!$Record.cldfs__Type__c}, Triggering CloudFiles Event > Type Equals 'document-processed'

This is how the final decision outcome looks like -

In order to apply CloudFiles Document AI on the desired document, we now need to first get processed event details. In order to do so, add a ‘Get Event Details’ action and put {!Record} as an event.

Refer to the GIF below to have a visual understanding of this step -

We will use CloudFiles' AI-enabled action ‘Query Document’ to classify the KYC document type - as Passport, Driver's License, or Other. There are two inputs required for this action: Process Document ID and Query. Please refer below to understand how to fill these input fields -

Refer to the gif to have a visual understanding of this step -

We have used the following Classification Prompt Query. You can customize it to suit your needs.

Please refer to the GIF below to have a visual understanding of this step -

Once the KYC documents are processed and classified into different document types, we will prompt for specific details about these documents, such as Passport ID and Passport Country. First, we will add a decision element to determine whether a document is a Driving License or a Passport based on the earlier classification query, and direct the flow accordingly. Then, we will add KYC-specific queries using the ‘Query Document’ action to retrieve crucial KYC details. Finally, we will populate these details into the relevant custom fields of the Account object. The detailed steps are given below -

We will add a decision element to classify whether the document is a Driving License, Passport, or neither. We will create two outcomes for this decision element, one for each document type, as shown below -

Refer to the GIF below for visual understanding -

Once the document is classified as a specific KYC type, we will use relevant prompts fed to the CloudFiles AI using the ‘Query Document’ action to extract specific information from the uploaded document. Different relevant queries can be written as text constants and applied as needed. It is advisable to make these queries highly objective and specific. The steps for this are the same as those used in the KYC classification query steps

For this tutorial, we have used three queries: one to fetch the Passport number, another for the Passport country, and a third for the Driver's license number. Refer to the queries below for an understanding of prompt writing. You can customize these queries to suit your requirements.

We will use ‘Update Records’ action for updating the above fetched information in the relevant fields of the Account object record. Follow these configurations for possible cases -

Update Records > Check Specify conditions to identify records, and set fields individually > Fill Account as Object

Input following Field-Value parameters to update records for various outcomes -

Default Outcome AI Output ← Neither Driving License, nor Passport detected For Driver’s License AI Output ← Driving License Detected Driving License Number ← Text from DL Number Query For Passport AI Output ← Neither Driving License, nor Passport detected Passport Country ← Text from Passport Country Query Passport Number ← Text from Passport Number Query Refer to the video given below for visual understanding -

Now that everything is setup, let’s test our flow. Follow the steps below to see this AI automation in action.

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