...
Overview
Experience.com’s LendingPad integration solution allows enterprise customers to automatically send surveys to loan customers during and after key moments in the lending/homebuying process. The LendingPad integration allows you to:
Ingest loan transaction data from LendingPad into Experience.com.
Map ingested data to campaigns within the account
Automate campaigns and surveys to loan customers based on role, transaction type, or location.
Transactions ingested from LendingPad into the XMP are labeled as verified transactions.
...
| Table of Contents |
|---|
...
Prerequisites for Configuring a LendingPad Integration
Several prerequisites must be met before Experience.com can access and ingest transaction data from LendingPad for a specific organization. LendingPad uses Zapier’s technology to integrate with Experience.com and other integrations. To integrate with LendingPad via Zapier, you will need:
A Zapier Starter package plan ($19.99/mo)
An API key from the organization’s LendingPad instance
An API key from the account’s ingestion set up in the XMP
Obtain an API Key from your Account’s Ingestion Setup
To create a new configuration, navigate to the Account Settings page and open the Ingestion Settings. Scroll to find and click LendingPad, and then click the blue “New Connection” button.
...
Once the connection is created, some information is required to verify and activate it.
Give the connection a name.
Enter a point of contact for the integration. This is someone that Experience.com may contact if an ingestion error occurs or if a re-configuration is needed for the integration.
...
Once a connection name and point of contact have been established, click the blue Verify & Connect button.
...
When the LendingPad configuration has been verified and connected, click back into it to access the API Key.
Locate the API Key and click the copy button to copy it to your computer’s clipboard.
...
Configuring the LendingPad Integration
To configure the integration between LendingPad and Experience.com, you will first need to create a Zap within Zapier. Then, a filter should be added so that transactions are only ingested when a loan status equals funded. Once a filter has been added, a zap can be created for Experience.com to retrieve the information. Finally, the data from LendingPad has to be mapped to fields available via Zapier. Once the fields are mapped properly, the connection can be finalized.
Take the following steps to get started:
Create a LendingPad Zap in Zapier
Log in to Zapier and click on Zaps from the menu.
On the Zaps page, click Create Zap.
In the search bar, search for and select LendingPad from the list of Apps.
Once you have chosen LendingPad as the app, select the trigger event: Loan Updated.
When the next screen pops up, you will be required to enter the API key that you retrieved from your LendingPad instance. Click Yes, Continue.
The API key can be found within the Settings>>Integrations>>Personal/API Keys within LendingPad.
When the API key is accepted, test the connection. Here, you will see sample loan data on your screen to ensure the information is pulling in properly.
Add a Filter to the Zap
From the list of Helpers, select Filter.
Under the Filter setup & testing section, set the condition to only continue if the field loan status equals funded.
Create an Action for Experience.com to Retrieve the Data
Once the condition has been set, go back to the LendingPad zap to add an Action.
For the App & Event, search for and select Experience.com. For the event, enter Retrieve LendingPad Transactions.
In the Account selection, select your Experience.com Account Name from the list.
If your Account is not on the list, click + Connect a new account.
To add the new Account, enter the API key that you gathered from the XMP LendingPad Configuration Screen.
Map LendingPad Fields to XMP Fields
The following fields from Zapier must be matched up and associated with the fields from LendingPad. For each field provided on the screen by Zapier, type or insert the corresponding field from LendingPad:
ZAPIER Fields | LendingPad Fields |
|---|---|
LoanId | Loan ID |
Loantype | Loan Type |
Loanstatus | Loan Status |
Loan_approved_date | Dates Approved |
Loanofficer | Loan Officer Name |
Loanofficer_email | Loan Officer Email |
Borrower_firstname | Borrower First Name |
Borrower_lastname | Borrower Last Name |
Borrower_email | Borrower Contacts Email |
Borrower_phone | Borrower Contacts Mobile Phone |
CO_Borrower_firstname | Co Borrower First Name |
CO_Borrower_lastname | Co Borrower Last Name |
CO_Borrower_email | Co Borrower Contacts Email |
CO_Borrower_phone | Co Borrower Contacts Mobile Phone |
Loanprocessor | Assignments Loan Processor Name |
Loanprocessor_email | Assignments Loan Processor Email |
Property_address | Subject Property Address Street |
City | Subject Property Address City |
State | Subject Property Address State |
Custom_field_one | Loan Status |
When the fields have all been mapped, click Retest & Continue to test that data is pulling into all of the places it should be.
Finally, click Done Editing, then turn the Zap on with the toggle at the top of the page.
Once the Zap is enabled, data will be pulled in from LendingPad and into Experience.com for transaction ingestion. Because of the API connection within the integration, data is transferred more often than on a daily basis. Transactions will typically be processed within hours of the status update.