Configure Data Targets
Use a Target Action to insert, update, upsert or delete Salesforce records using data available at that point in the sequence. The Target defines the object, operation, matching identifier, record count and field mappings.
Add the Target at the correct position
Select the plus button in the Actions sequence and choose Target. For an existing Target, select its card and use Edit in the Target detail section.
In an Outbound Payload, Targets run after HTTP Response. For Inbound, Email and CSV Import, place the Target after the Actions that supply its data. Place child Payload callouts before Targets.
The Action sequence determines order. There is no separate Target Order control in the v1.53 Actions workflow.
The New Target modal creates the Target before its individual field mappings are added.
Choose the object and operation
Select the Salesforce object, then choose the operation:
Insert creates a new record.
Update changes a record identified by the configured matching value.
Upsert creates or updates using the configured identifier.
Delete removes the identified record.
For operations that identify an existing record, configure a stable Id or eligible external identifier and map its value. Do not rely on a display name being unique.
Test Delete with controlled records and a narrowly defined source because a valid mapping can remove real Salesforce data.
Choose Single Record or Multiple Records
Single Record builds one Salesforce record for that Target execution.
For Multiple Records, configure Records From. Choose Payload Data, select an earlier Action and then select its collection. This can be queried records, a parsed body array, earlier Target records or another compatible published collection.
For CSV Import, choose CSV Import and CSV Rows to process the current chunk's source rows. A nested array can produce more than one Target record per source row.
Add field mappings
Save the Target first, then select its Action card and add field mappings from its detail view. The New Target modal creates the Target configuration; individual fields are configured afterwards.
Add the Salesforce fields the operation needs. Set each Value Source, then select its value or earlier Action output. Include required fields, the identifier for update/upsert/delete and any relationship fields needed by the business process.
A lookup can use a Salesforce parent Id or an eligible parent external-ID field through Parent Field. See Map parent lookups by external ID.
Use supported transformations and conversions to match destination field types. Save and inspect the configured field list before running.
Review results and partial success
Run with representative inputs and inspect the Target on the Job timeline. Check the actual records and errors as well as the overall Job status.
For CSV imports, ordinary row failures allow valid records to commit and processing to continue. A source row can have successful outcomes in one Target and failures in another. A fatal chunk failure rolls back that chunk, while earlier chunks remain committed.
Other entry points and partial-success settings have their own transaction behaviour. Do not infer whole-sequence atomicity from one Target's success.