Use Data Targets when a Payload should create, update, or upsert Salesforce records from data handled during the run.

A Data Target defines the object, operation, identifier, and field mappings. Payloads then runs the target after it has parsed the inbound data or API response.

For the field-level mapping options, see Map Data Target fields.

Use a Data Target when Salesforce should keep a value from:

In the Stripe demo, Data Targets update an Opportunity after a checkout session response, update an Opportunity after a Stripe event, create follow-up Tasks from Stripe line items, create a Task from an email, and update a Credential after a bearer token refresh.

The Payload type decides where the Data Target appears.

For Full Callout and Credential Payloads, Data Targets belong to the Response side because they write values returned by the external API.

For API Push Into Salesforce and Email Service Payloads, Data Targets belong to the inbound Request or Incoming Email side because they write values received by Salesforce.

Full Callout Data Targets usually write values from the API response back into Salesforce.

API Push Into Salesforce Data Targets usually write values from the inbound request into Salesforce.

Choose the Salesforce object first, then choose the operation.

Use Insert when Payloads should always create a new record.

Use Update when the inbound data includes a reliable identifier for an existing record, such as a Salesforce Id or external id.

Use Upsert when the same payload may need to create a record the first time and update it later.

For updates and upserts, set the Identifier to the field Payloads should use to find the record. Do not rely on names or display values when a stable Id or external id is available.

Open the target modal when you need to review or change the target behaviour.

The target modal controls which Salesforce object Payloads writes to and how it identifies records.

Use Single Record when one target run should create, update, upsert, or delete one Salesforce record.

Use Multiple Records only when the Payload has a source array. The source array decides how many records Payloads should build. Each item in that source array becomes one record in the target result list.

For a multi-record target, Map Record Count To can point to:

In the Stripe event demo, the line item Task target maps Record Count to the inbound array at $.data.object.line_items.data. If the event contains two line items, the target builds two Task records.

A multi-record target needs a source array because the array controls the target record count.

Target Fields define the Salesforce fields Payloads writes.

Keep the mapping narrow. Write the fields the integration owns or explicitly needs to maintain. Avoid mapping every value in the request just because the value exists.

The email demo creates a Task from incoming email content, using inbound email fields for the Subject and Description and static values for fields such as Status and Priority.

Data Targets can combine inbound values and static values to create a useful Salesforce record.

Targets run in order. A later target can use field values produced by an earlier target.

This is useful when the first target creates or updates a parent record and the next target needs that record id. In the Stripe event demo, the Opportunity target runs first. The line item Task target can then use the Opportunity target's Id as the Task WhatId.

Keep chained targets ordered deliberately. If target 2 needs a value from target 1, target 1 must have the lower order number.

Before testing, check that:

After testing, open the Job and review the target output. It shows the object, operation, field values, record id, and success or error result.