Mapping Values to a Custom Json Outbound Integration

When mapping values and fields in a custom Json outbound integration, use "dot notation" to define where each value being mapped should be placed in the request body.

(This article assumes that you understand the basics of how Json documents are structured. There are numerous resources and tutorials online that cover the basics of Json data structures.)

Json documents consist of hierarchically organized collection of Json objects, properties and arrays.Use dot notation to map the structural path to each value you need to send to the recipient of your LeadConduit flow's Custom Json outbound step.

It's probably easiest to see how dot notation works by looking at an example.Here's a typical json request body:

Note that it consists of a json object that consists of several root-level json properties (Named "lead", "phones", "leadEmail", "address", "passcode", and "programTypeCode") each of which may have as their values either a simple value (as do "leadEmail", "passcode", "programTypeCode"), or a collection of child properties (as do "lead" and "address") or an array of child objects (as does "phones").

To map a value to a root-level property like "leadEmail", the path in this case would simply be the property name: leadEmail

To map a value to a child property, like "FirstName" which is a child of the root-level property "lead", the path would be lead.FirstName

When a property has as its value an array of one or more child objects, such as "phones" which has as its value an array of one or more json objects each of which has two properties ("PhoneNumber" and "PhoneType"), each element of the array is represented a numeric subscript that relates the components. For instance, to map phone_1, the path for that element's PhoneNumber would be phones.0.PhoneNumber and the path for that element's phoneType would be phones.0.PhoneType.Similarly, for phone_2 the paths would be phones.1.PhoneNumber and phones.1.PhoneType. Subscripts must be assigned sequentially beginning with zero.

Here is an example of what the mappings for the above Json request body would look like in LeadConduit: