SharePoint Contract Upload to Salesforce Record Linker

Overview

FlowLibs - SharePoint Contract Upload to Salesforce Record Linker automates the creation of Salesforce Contract records when contract documents are uploaded to a SharePoint document library. The flow parses the file name to extract the account name and contract type, looks up the matching Salesforce Account, and creates a linked Contract record with metadata including a direct link back to the SharePoint document.

It ships in an Off state so admins can configure environment variables and verify connector authentication (SharePoint Online and Salesforce) before enabling it.

Use Case

Sales and operations teams frequently upload signed contracts to SharePoint but must then manually create corresponding records in Salesforce to maintain CRM accuracy. This flow eliminates that manual step by detecting new contract uploads in a dedicated SharePoint document library, parsing the file name using the convention AccountName - ContractType.pdf, looking up the Salesforce Account by name, and creating a Contract record tied to that Account with status, dates, and a link to the source document. Missing accounts are handled gracefully with a warning compose for downstream alerting.

The flow is ideal for teams that:

• Detect new contract uploads in a dedicated SharePoint document library
• Parse the file name using the convention AccountName - ContractType.pdf
• Look up the Salesforce Account by name
• Create a Contract record tied to that Account with status, dates, and link to the source document
• Handle missing accounts gracefully with a warning compose for downstream alerting

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

File naming convention

The flow expects uploaded files to follow the pattern AccountName - ContractType.extension (e.g. Contoso - NDA.pdf, Fabrikam - Master Services Agreement.docx). If the contract type is omitted (e.g. Acme.pdf), the flow defaults to 'General'. Document this convention for your contract uploaders.

Change the Salesforce target object

Update the flowlibs_SalesforceContractObject environment variable to target a different Salesforce object (e.g. Opportunity, CustomObject__c). Ensure the target object has the fields: AccountId, Name, Status, StartDate, Description, or remap the Create action accordingly.

Point at a different SharePoint library

Update flowlibs_ContractDocLibraryId with the GUID of the target document library and flowlibs_SharePointSiteURL with the correct site URL. The trigger will start watching the new library on next save.

Known designer warning (false positive)

The Flow Checker shows 6 errors on the 'Create Contract Record in Salesforce' action because the table parameter is bound to an environment variable via @variables('varSalesforceObject'). The designer cannot resolve the Salesforce schema dynamically, so it flags all field mappings as missing. These are designer-only false positives and do not affect runtime execution - the same pattern is used for Excel dynamic tables and Dataverse CreateRecord with variable entity names.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

split(first(split(triggerOutputs()?['body/{FilenameWithExtension}'], '.')), ' - ')

trim(first(outputs('Compose_Parse_File_Name')))

if(greater(length(outputs('Compose_Parse_File_Name')), 1), trim(outputs('Compose_Parse_File_Name')[1]), 'General')

concat('Name eq ''', outputs('Compose_Account_Name'), '''')

first(body('Lookup_Salesforce_Account')?['value'])?['Id']