This Article covers how to map nested JSON data to eLead fields within improveit 360 without using a third-party application like Zapier. If you do not have an example payload you will need to ask the lead provider to send you the payload, exactly as they will be sending eLeads into the system. You will need to copy the syntax of the payload exactly.
If you need to map fields from the eLead to other subsequent records created during eLead conversion, see also: Standard eLead Field Mapping records
Out of the box the only way eLead fields will be populated is if the lead provider sends the exact Field API Names within their payload, for example the lead provider would need to send in...
{ "i360core__First_Name__c": "Joe",
"i360core__Last_Name__c": "Dirt" }
...In order for the system to receive "Joe Dirt" as the Contact Name.
However, most lead providers will not modify their payload and will not know improveit 360's API Names. Therefore, the JSON field labels within the string will need to be mapped using JSON Mapping records.
This Article covers how to map fields which are not nested within a JSON string, as well as fields which are nested within sub headers within the JSON string. For this reason, it is necessary to have a copy of the exact payload from the lead provider.
Example payload:
{ "first_name": "Joe",
"last_name": "Dirt",
"email" : "jdirt@thedirtshow.com",
"sourceName": "HomeAdvisor",
"address": {
"street_address": "4249 Easton Way",
"subAddress": {
"city" : "Columbus",
"zip_code": "43215" }
}
}
In the example above, we will need to map all of the Field labels within the payload because none of them use improveit 360's API Names.
Navigate to the eLead Endpoint JSON Mapping Tab from the App Launcher
Note: Nested portions of JSON will need to include the header and sub-header names and they must be separated with a period. For example, in the string above, "City" is nested beneath address and subAddress so you would write that as: "address.subAddress.city"
Name with Source specific labels to avoid duplicate API Names on the JSON Mapping metadata records.
NEW SCREENSHOT
Also Note: Source Name is determined one of two ways:
1. A header value sent in the request payload with one of the following names: provider, leadprovider, lead-provider, source, source-name
2. A JSON property with one of the following names: provider, leadprovider, leadProvider, lead-provider, source, source-name, sourceName, i360core__Source__c
NOTE: Because my example string above contains the appropriate JSON property tag for Source Name (sourceName), I do not need to create that as a JSON mapping row.
If you receive this Error message when trying to Save, please ensure that your organization has an eLead integration setup. See also: Setup eLead integration Endpoint (internal)
Comments
0 comments
Article is closed for comments.