Skip to main content
You already work your files in Arive. Connect it once and your loans show up here, statuses stay in step both ways, and on most loans the client’s own details keep themselves current as the file moves. Nobody re-types a client. The Arive integration is included on Free, so you don’t need a Leaf360 upgrade to connect it. Other integrations require an upgrade. See Plans and billing.

​
Where to find it, and who sets it up

Click your profile at the bottom left, then Account Settings. Scroll down to Data & Integrations and select Integrations. The Arive card sits among the built in connectors, described there as a loan processing platform connected with issued credentials and a portal link. For that same path screen by screen, see Connecting Arive.
The Arive card is administrator only. It doesn’t appear on the Integrations shelf for anyone else, and the connection it creates is shared by the whole company rather than owned by one person.

​
Connecting

Opening the card starts on a Settings tab with a choice of connection mode: If you don’t know which of the two your company uses, ask before choosing. The credentials each mode needs are different. Under Direct API, an administrator enters the Arive Portal URL, then a Client ID, Client Secret and account key, each saved with its own button. A Test Connection button confirms the credentials work.
On a Zapier connection, the panel on the right reads Setup Complete once your Zapier keys are all saved, or Setup Incomplete while one’s still missing. You don’t need Direct API credentials for Zapier.
Zapier can send the same supported loan details as the Direct API, but what arrives depends on the fields your Zap sends and how they’re mapped. Saving your keys doesn’t add those fields to an existing Zap. Ask whoever manages your Zap to update the field keys and mapping for the details you need. If you need the current field list, contact support. Supported details include:
  • Co-borrowers on the lead as well as the loan
  • Up to ten employment entries
  • Housing expenses and both DTI figures
  • Key dates from LE and CD through funding

​
Two mapping tabs, two directions

Once connected, Arive opens several tabs, and two of them are about keeping statuses lined up between the two systems. Status Mapping is the writeback direction: when a loan’s status changes in Leaf360, this mapping decides what status gets set on the matching loan back in Arive. It only appears in the Direct API mode. Arive to Leaf360 Mapping is the other direction: when a loan’s status changes in Arive, whether by someone updating it there or by Leaf360 pulling the latest version, this mapping decides two things at once, which of your company’s own loan statuses the Leaf360 loan should move to, and which lead stage and status the matching lead should carry. Each row can also be set to skip updating the loan status altogether, for an Arive status where you’d rather leave the Leaf360 side untouched. An administrator can create a new loan status or lead status right from this tab if the one they need doesn’t exist yet.
Both mapping tabs, along with Loans, Webhooks and the two event log tabs, only open once the connection shows as connected on the Settings tab.

​
Pulling and syncing loans

The Loans tab searches Arive directly, by borrower name, borrower email or loan number. Select one loan or many and click Sync to Leaf360 to bring them in, or open a single loan and use Sync Loan Status to refresh just that one. Based on the mapping above, here’s what comes across on a synced loan:
  • Loan amount, credit score, purchase price, down payment and appraised value
  • Loan type (FHA, VA, USDA or conventional), lien position and amortization details
  • Occupancy and the property address
  • LTV and DTI figures
  • Estimated and actual closing dates On the borrower side it carries across the primary borrower and any co-borrowers, including date of birth and address, and Leaf360 checks co-borrowers by email, phone, name and date of birth together so the same person isn’t added twice.
On a loan that has just funded as a purchase, the borrower’s address on their lead record updates to the property they bought. On every other loan, their stated home address is used instead, so a loan still in progress doesn’t overwrite where a borrower says they currently live.

​
Arive loans imported by file

Loans brought in through the general loan importer on the Loans page recognize Arive’s own column headers on their own. So you don’t have to map anything when you upload a file exported straight out of Arive. That includes military service status and preferred language for both the borrower and co-borrower, alongside the rest of the borrower and loan fields. See Import Data for importing outside of a specific loan pipeline.

​
Common problems

It’s administrator only. If Arive isn’t on the shelf at all, you’re on a company account, and an administrator at your company has to follow the connection steps and enable it for you. Ask them to set it up, or to check whether it’s already connected.
They only open once the Settings tab shows a working connection. Save credentials and confirm with Test Connection first.
One of your Zapier keys isn’t saved yet. Go ahead and fill in the missing one and the panel switches to Setup Complete.
Check the Arive to Leaf360 Mapping tab. The Arive status that loan carries may be mapped to a different Leaf360 status than you expected, or set to skip loan status updates entirely.
Writeback only runs in the Direct API mode, and depends on the Status Mapping tab having an entry for that status.
Last modified on September 3, 2026