Document Mapper

Introduction

The CloudFiles Document Mapper flow action enables execution of a Document Mapper configuration directly from a Salesforce flow. This action processes a document, extracts structured data using the configured mapping, and then creates or updates Salesforce records automatically. It's particularly useful for converting documents such as invoices, forms, or contracts into Salesforce records as part of an automated process without requiring user interaction.

What This Action Does

The Document Mapper action runs a pre-created Document Mapper configuration against a provided file. When executed, CloudFiles processes the document using the configuration specified by the Config ID. Based on that configuration, Salesforce records are created or updated automatically.

If a Record ID is not provided, the action creates new Salesforce records exactly as defined in the document mapper configuration, including a primary record and any related or child records such as line items.

If a Record ID is provided, the action updates the specified Salesforce record and creates any related records defined in the configuration, enriching existing records with data extracted from documents while supporting complex parent-child record creation.

The action runs asynchronously and publishes events once processing is complete.

Input Parameters

Config ID

This parameter specifies the Document Mapper configuration to use when processing the document. The configuration controls which Salesforce objects are created or updated, which fields are populated, and how parent-child relationships are handled. It also defines the prompts used by Document AI to extract data from the document.

Resource

The Resource parameter represents the file to be processed by Document Mapper. This input must be provided as an Apex-defined variable representing a CloudFiles Resource. The document referenced by this resource is the file from which data will be extracted and mapped to Salesforce records.

To Process a Salesforce File

To specify a Salesforce File to be processed, input parameters as follows (please note the parameters are case sensitive):

1. Library - salesforce (please note the parameters are case sensitive)
2. FileID - The ContentDocumentID of the Salesforce File to be processed.

To Process an External Storage File

If you are using the CloudFiles: Document Management package as well, then you can process a file in connected external storage. In order to specify an External Storage File to be processed, input parameters as:

1. 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). Please note the parameters are case sensitive.
2. Drive Id - The Id 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.
3. fileid - The unique identifier (Resource Id) of the file that is to be processed.

Record ID (Optional)

The Record ID parameter allows you to specify an existing Salesforce record to update. When this value is provided, the Document Mapper run action updates the specified record using the extracted data. Any related or child records defined in the configuration are also created as part of the same execution. If this parameter is not provided, the action creates new Salesforce records based on the configuration.

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 Mapper Run event is published. This event includes information about the processed document and the records involved in the execution and can be used to trigger platform event flows to perform any post-processing actions.