SharePoint CSV Bulk Uploader to Salesforce

Overview

This flow automates bulk data loading into Salesforce by monitoring a SharePoint document library for new CSV drops. When a file lands, it spins up a Salesforce Bulk API 2.0 job against the configured target object, uploads the CSV payload, closes the job to start asynchronous processing, and notifies Teams with submission details (or a failure alert if anything breaks). It ships as a stopped flow inside a packaged solution and is driven entirely by environment variables — zero hard-coded endpoints, object names, or IDs.

Use Case

Operations teams frequently need to ingest large record sets into Salesforce on a recurring basis — nightly order exports, weekly contact refreshes, territory realignments, partner lead feeds. Manually running Data Loader or submitting Bulk jobs through Workbench is error-prone, gated on a single operator, and leaves no audit trail. By dropping a CSV into a governed SharePoint folder and letting this flow handle the rest, the business gets a repeatable, auditable, and multi-operator-friendly upload pipeline with Teams-based visibility into every submission.

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.

Swap the target Salesforce object

Update the flowlibs_SalesforceBulkTargetObject env var — no flow edits required. Valid values are any Salesforce object API name reachable by the connection (Contact, Account, Lead, CustomObj__c, etc.).

Switch operation mode

Change flowlibs_SalesforceBulkOperation to insert, update, upsert, or delete. For upsert, ensure your CSV has an external ID column and that the connector bulk job references it (extend Create_Salesforce_Bulk_Job inputs with parameters/externalIdFieldName if needed).

Tighten polling interval

The trigger is set to 5-minute recurrence; lower to 1 minute by editing triggers.When_A_New_CSV_Is_Uploaded.recurrence.interval. Beware of connector throttle limits on very tight intervals.

Add CSV validation

Insert a Compose or schema-parse step between Get_CSV_File_Content and Create_Salesforce_Bulk_Job to reject malformed headers before creating a bulk job you would then have to abort.

Route failures elsewhere

The Post_Failure_Alert_To_Teams action uses the same Teams variables; split it into its own env vars if failure notifications should go to a separate ops channel.

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.

@triggerOutputs()?['body/value']

@triggerOutputs()?['body/Id']

@{triggerOutputs()?['body/Name']}

@body('Create_Salesforce_Bulk_Job')?['id']

@{utcNow()}

runAfter: { Get_CSV_File_Content: [Failed, TimedOut], Create_Salesforce_Bulk_Job: [Failed, TimedOut], Upload_Job_Data: [Failed, TimedOut], Close_Job_To_Start_Processing: [Failed, TimedOut] }