A Target Field maps one Salesforce destination field. Choose the destination first, then select the value available to this Target Action.

Configure these mappings through the Target Action's custom editor, not through standard Target Field record pages.

For example, after an external checkout response, map a Salesforce URL field from HTTP Response and its checkout URL Element. For a fixed Salesforce picklist value, choose Static Value and enter the accepted value.

Payload Data covers earlier request or response content, Query records, Target results and published Flow or child Payload outputs. Select the actual producer rather than using the legacy Inbound Element, Queried Field or Target Field source categories.

Static Value supplies a fixed value. Global Variable supplies supported runtime values. Dynamic Input and Credential sources are available only in the editors and contexts that support them.

Only earlier Action outputs are available. If a required value is absent, check the producing Action, its position and any output publication before changing the consumer.

Update, Upsert and Delete need to identify the record the Target should affect. Map the configured identifier from a stable Salesforce Id or external key.

A parent lookup mapping is separate from the Target's own matching identifier. For example, a Contact external key identifies the Contact while AccountId links it to its Account.

For a lookup or master-detail destination, Parent Field can select Id or an eligible parent external-ID field. Supply the corresponding kind of value. See Map parent lookups by external ID.

For a multiple-record Target, Records From defines the source collection. Map fields from the current item so each Salesforce record receives its own values.

A value outside that collection can intentionally be shared across every record. Check that this is appropriate for relationship IDs, owner values or fixed status fields.

A later Target can use the output of an earlier Target to establish relationships, such as linking generated Tasks to an Opportunity. Select the earlier Action and its record field through Payload Data.

Test blank values, invalid numbers or dates, missing identifiers and relationship keys as well as normal data. Check required fields, validation rules and restricted picklists in the destination org.

Open the Job and inspect the Target's mapped records and outcomes. If a value is wrong, compare it with the producer's recorded output. For CSV, inspect each source row's outcomes before rerunning it because another Target may already have succeeded.

See Map data between Actions.