Back to DocuFlow

Off the Case, and back onto it

Every customer's Salesforce is different, so the mapper is the feature. A document pulled off a record remembers it, which turns the round trip, extract the file on a Case and write the answer back to that Case, into a mapping rather than a project.

Map extracted data
onto any object

Fill each field from an extracted value, a property of the document, fixed text or a small template, shaped by a transform that knows what money and dates look like on a scanned page. Parent records are found by searching for them, and a repeated table becomes child rows in the same pass.

Destination · SalesforceNorthwind Health Cloud
CaseCase
What to doCreateUpdateUpsert

Changes a record that already exists.

Field mapping

What each Case field is filled with.

  • SubjectTextSubjectTemplatePA {{service.cpt}} · {{patient.lastName}}As written
  • Status*PicklistStatusFixed textDecision PendingAs written
  • Member IDTextMember_ID__cExtractedMember IDTrim whitespace
  • Requested Service DateDateRequested_Service_Date__cExtractedRequested startDate (YYYY-MM-DD)
  • CPT CodeTextCPT_Code__cExtractedCPT codeAs written
  • DocuFlow LinkURLDocuFlow_URL__cDocumentLink in DocuFlowAs written

Related records

Fill a lookup by searching for the parent, so nobody has to paste eighteen-character ids into DocuFlow.

AccountId find the Account whose

NPI__cis exactlyExtractedProvider NPI
If nothing matchesstop and report it

Try it

Builds the record against the most recently processed document in this queue and checks it against Salesforce. Nothing is written.

Using aetna-pa-whitfield.pdf, this would update one Case keyed on 5003h00000QxT2kAAF.

  • Case.BusinessHoursId is required and nothing fills it. Salesforce sets it from the org's default hours.

Salesforce would accept this record.

Lookups

AccountId: found Lakeside Orthopedics by NPI__c

The record

{
  "Subject": "PA 29881 · Whitfield",
  "Status": "Decision Pending",
  "Member_ID__c": "W2918847301",
  "Requested_Service_Date__c": "2026-10-06",
  "CPT_Code__c": "29881",
  "AccountId": "0013h00000Lk9QpAAJ"
}

Included

Watches files, not recordsattaching a file never touches the record, so DocuFlow watches the files
Classic and modernNotes and Attachments are read alongside Files
Filters that know the fieldpicklists offer their values, dates accept TODAY
Record fields in intake rulesonly Cases whose Status is Open, with nothing to build
Match by nameoffers only fields whose names agree, never a formula
Try itthe delivery code with one flag set, so the preview cannot drift

Bring the forms your team still retypes

A working session on your own documents: one queue, your fields, your rules, and a count of what would have gone straight through.