Salesforce output

Write rows back to Salesforce: insert, update, upsert or delete, 200 records a request, with every rejected record reported.

Category: Output
Connection: Salesforce
Also known as: reverse etl, crm, sobject, sfdc, upsert, push

What it does

Writes the incoming rows back to Salesforce (through a saved Connection), 200 records a request. Insert, update, upsert on an External ID, or delete. Each column's name is the Salesforce field name, so use Manage Columns upstream to line them up. Every record Salesforce rejects is reported individually, with Salesforce's own reason.

Inputs and outputs

Inputs	One.
Outputs	None. This node ends a pipeline.

When to use it

Push a score, segment or status you calculated back onto the CRM record
Sync accounts or contacts from a warehouse or another system into Salesforce
Keep a Salesforce object up to date on a schedule, matched on your own key

Examples

Create records

Object: Account · Operation: insert

Update by Id

Object: Opportunity · Operation: update

The rows need an Id column.

Keep in sync

Object: Account · Operation: upsert · External ID: Legacy_Id__c

Re-runnable: creates what's new, updates what isn't.

Tips

A request Salesforce may already have processed (a timeout or a dropped connection after sending, a 500) is never sent again, because a resent insert is a second record. The run stops and names the batch; check the object before re-running (Upsert makes a re-run safe). A 429, a 503 or a connection that never opened is retried.
Upsert is the one to reach for on a schedule: it creates what's missing and updates the rest, so re-running it doesn't duplicate anything.
Upsert matches on a field marked External ID in Salesforce. The standard Id is not accepted there; use update for that.
A Test run never writes to Salesforce.
Delete moves records to the Salesforce Recycle Bin, where your administrator can restore them for 15 days. Trinium never deletes a record permanently.
Salesforce has no rollback across requests: “fail” protects the batch of 200 that failed, but batches already accepted stay written.
“Send empty columns as null” CLEARS the field in Salesforce. Leave it off unless clearing is what you mean.