Push to Salesforce
Push CSV data from a Multi FileFeed into Salesforce using the Bulk API.
Push to Salesforce writes rows from your Multi FileFeed (MFF) into a Salesforce sObject using the Bulk API 2.0. Use it to insert, update, or upsert Salesforce records at the end of an MFF, after your data has been cleaned and validated.
Availability: Beta. Requires the
WorkflowsSalesforcePushfeature. Contact your OneSchema support representative if you do not see this transform.
What it does
- Input: one or more CSV files.
- Output: none for downstream transforms — this is a terminal (sink) node. It writes records directly to Salesforce rather than passing files onward.
- The transform maps columns in your input to fields on the target sObject and submits the records through Salesforce's Bulk API 2.0, which is designed for high-volume inserts, updates, and upserts.
When to use it
- You've cleaned and validated vendor or partner data and need it loaded into Salesforce as Leads, Contacts, or custom object records.
- You're syncing data from another system (like a data warehouse export) into Salesforce on a schedule.
- You want to upsert records using an external ID field instead of Salesforce record IDs.
How to configure it
In the MFF builder, add a Push to Salesforce node at the end of the branch that produces your cleaned CSV file.
Settings
| Setting | Description | Default |
|---|---|---|
| sObject type | The Salesforce object to write to, for example Contact or a custom object. | None selected |
| Operation | The write operation to perform: insert, update, or upsert. | insert |
| External ID field | The field used to match existing records when the operation is upsert. Required only for upsert. | None selected |
| Field mappings | The mapping from input columns to Salesforce fields on the target sObject. | Empty |
| Salesforce account | The connected Salesforce credential to use for the push. | None selected |
Configuration tips
- Use Fetch Salesforce Schema upstream to confirm field names and types before building your field mappings.
- If you choose upsert, make sure the external ID field is marked as an External ID field in Salesforce and is populated in every row.
Example
Setup
An input CSV file with columns Email, FirstName, LastName, mapped to the Contact sObject with operation set to insert.
Result
One new Contact record is created in Salesforce for each row in the input list.
Troubleshooting
Records fail to insert or update
- Check the field mappings against the target sObject's field names and types; type mismatches (like text into a number field) are a common cause.
- Confirm required fields on the sObject are included in your mapping.
Upsert fails with a missing external ID error
- Confirm External ID field is set and that the field is marked as an external ID in Salesforce's object setup.
See also
Updated 1 day ago