Elements define the shape of API or email content and, where content is being generated, the source of each value. An Element can represent a body field, object, array, header, parameter or URL modifier.

Configure Elements inside the relevant Action's custom editor. For example, select HTTP Request and use Body to model an Outbound request. Do not edit internal Element records through their standard Salesforce record pages.

For Outbound, HTTP Request builds the content sent to the external API and HTTP Response models the content received from it.

For Inbound, HTTP Request models what the caller sends and HTTP Response builds what the caller receives. The same words describe different directions because the initiator is different.

Select Body, Headers, Parameters or Modifiers within the relevant Action where available. Check the selected Action heading before adding a field.

An Object groups children. An Array repeats a structure. Leaf Elements represent values such as strings, numbers or Booleans according to the content model.

For example, line_items can be an Array whose children describe a product and amount. The Array's collection source controls repetition; the amount child maps the current item's amount.

Use the root structure expected by the API. If it expects a top-level array, configure an Array root rather than wrapping it in an extra Object.

Received content needs the Elements the integration will use. You do not have to model every unused property in a large API response.

HTTP Response models the received fields that later Actions can use.

When an Element builds outgoing content, choose its Value Source. Payload Data reads a field or output from an earlier Action. Select that Action, then the required output or field.

Static Value supplies fixed content. Dynamic Input declares a value to be supplied when the Payload runs. Global Variable and Credential sources are available in supported editors. Apply a Transformation where the selected value needs a documented conversion or calculation.

For example, create an Opportunity Query before HTTP Request, then map a request Element from that Query's Amount field using Payload Data. Map a line-item Array from its child collection and map child fields from the current line item.

A field inside a repeated Array normally needs the current item. Selecting an unrelated scalar can repeat the same value for every item.

For Targets that consume received arrays, choose the collection in Records From and map fields from that collection's current row. Use fields outside the collection only when their shared value is intentional.

CSV schemas are a special case: leaf values remain Strings and the CSV Import Action supplies a row collection. See Configure a CSV Import Payload.

Run a controlled test and compare the resulting Job's Action data with the configured structure. Check property names, nesting, arrays, blank values, types and transformations.

If a value is missing, first check the producing Action's recorded output, then the consuming mapping. Continue with Map data between Actions.