For any Lead Providers who are sending JSON in their eLead payload, you are able to alter the data being sent in from the Lead Provider using Zapier and their Paths feature.
Use case: The lead provider may be sending in "Replacement Windows" but your Product Category in the system is "Windows" you want to change the payload so that improveit 360 receives "Windows" as the Product Category of Interest. The lead provider may also be sending in Source or Lead Source names which do not match the values in the system. These would need to be remapped using the method below.
Get the webhook URL and give this to the lead provider to send eLeads to.
You can use POSTMan to send test eLeads into Zapier to test how the data is parsed and mapped.
Here is a sample Payload from Angi for reference:
{
"name": "John Doe",
"firstName": "John",
"lastName": "Doe",
"address": "1234 Elm Street",
"city": "Anytown",
"stateProvince": "CA",
"postalCode": "90210",
"primaryPhone": "5559876543",
"secondaryPhone": null,
"email": "johndoe123@example.com",
"srOid": 123456789,
"leadOid": 987654321,
"fee": 0.0,
"taskName": "Metal Roofing - Install or Replace",
"comments": "Customer did not provide additional comments. Please contact the customer to discuss the details of this project.",
"matchType": "Lead",
"leadDescription": "Standard",
"spEntityId": 567890123,
"spCompanyName": "Example Exteriors LLC",
"leadSource": "AngiesList",
"trustedFormUrl": "https://cert.trustedform.com/abcd1234abcd5678abcd9012abcd3456abcd7890",
"primaryPhoneDetails": {
"maskedNumber": false
},
"interview": [
{
"question": "What type of project is this?",
"answer": "Completely replace roof"
},
{
"question": "What roofing material do you want?",
"answer": "Metal"
},
{
"question": "How tall is your house/building?",
"answer": "2+ stories"
},
{
"question": "When do you need this work done?",
"answer": "Not sure - still planning/budgeting"
}
],
"automatedContactCompliant": true,
"automatedContactConsentId": "123e4567-e89b-12d3-a456-426614174000"
}Your Zap will look something like this:
Add Paths for every unique Product Category value that is coming from the lead provider, and select the Conditions for when the Zap should alter the value, in this case we are looking for an exact match to the Product Category value being sent in from the lead provider.
When the Value is an exact match to "Install or Replace Exterior Trim"...
we want the system to use "Siding" instead as the Product Category value for all the eLeads which come in with "Install or Replace Exterior Trim" as the Product Category of Interest.
You may want to look at the existing Lead Source records in your improveit 360 system and make sure you are mapping in the correct Lead Source Name and Source Name:
Next you will want to create a Fallback Path for records that do not have any of the specific Product Category values, to create an eLead record with an Unknown Product Category.
When creating the record, you will need to select a value in the Restricted Picklist field on the eLead object. In this customer's system, they have a value of "Unknown" so we will use this for the Interested In value:
In the Comments field, we will map the Category payload coming from the Lead Provider. This ensures we still see the product category data from the lead provider.
This ensures that when the eLead is received by improveit 360 that you will see the Product Category sent from the lead provider, even if it is not a value in your system's Product Categories.
From the Catch Hook element, you should see the Data from the payload
The Create Record element will create an eLead record.
Map the Fields to the eLead object
Map the Fields:
All the extra fields should be mapped to the Comments field.
The eLead should always get created regardless of their being enough Data points to convert the eLead to an Account/Contact.
Comments
0 comments
Article is closed for comments.