Arive logoLeaf360

Your Arive loans. Synced to your mortgage CRM.

Connect Arive once and your loans, borrowers and statuses come across into Leaf360. On Direct API, status changes move both ways. Here is exactly what moves, what an admin needs before connecting, and the guides that walk through it.

Get Started

What moves, and in which direction

Arive to Leaf360

Configured on the Arive to Leaf360 Mapping tab. When a loan’s status changes in Arive, or Leaf360 pulls the latest version, that tab decides which of your own loan statuses the file moves to and which lead stage and status the matching lead carries. Any row can be set to skip.

Leaf360 back to Arive

Direct API only. When a loan’s status changes in Leaf360, the Status Mapping tab decides what status gets set on the matching loan in Arive. It writes back only for statuses that have an entry there.

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
  • The primary borrower and any co-borrowers, with date of birth and address; co-borrowers are matched on email, phone, name and date of birth together, so the same person is not added twice

Before you connect

Four things to have ready before you open the card.

An administrator

The Arive card is administrator only, and the connection it creates is shared by the whole company. If you do not see the card, an admin at your company has to connect it.

Direct API or Zapier

Your company uses one of the two. The credentials differ, so ask before you pick. In Arive, the option lives under User Settings, then API, as Integrate with Arive (not Integrate with UWM, which is a different integration).

Direct API credentials

The Arive Portal URL, then a Client ID, Client Secret and API Key generated in Arive and pasted into Leaf360. Use Copy in Arive rather than letting a browser autofill the fields.

LOS Email Alias

Only if the email you use in Arive is not the one you sign in to Leaf360 with. Put the Arive email here so loans match to you.

Setup, step by step

The short version. Each step links to the guide with the screens.

  1. Open the Arive card

    In Leaf360, click your profile at the bottom left, then Account Settings. Under Data & Integrations, choose Integrations and select Arive.

  2. Pick the mode and enter credentials

    Choose Direct API or Zapier. For Direct API, paste the Portal URL, Client ID, Client Secret and API Key, add the LOS Email Alias if you need one, and save each with its own button.

  3. Test the connection

    Click Test Connection. The mapping, Loans, Webhooks and event log tabs only open once the Settings tab shows a working connection.

  4. Map statuses

    On Arive to Leaf360 Mapping, decide which loan status and lead stage each Arive status moves a file to, or set a row to skip. On Direct API, Status Mapping sets what a Leaf360 status change writes back to Arive.

  5. Bring loans in

    On Direct API, the Loans tab searches Arive by borrower name, email or loan number: select one loan or many, click Sync to Leaf360, and subscribe to webhook events so later changes keep flowing. On a Zapier connection, export from Arive and upload the file through the loan importer instead.

What it looks like in a week

One file, start to finish, with the pieces this integration actually does.

  1. You take a new application in Arive. On the Loans tab in Leaf360 you search the borrower’s name, select the file and click Sync to Leaf360. The loan arrives with its amount, type, property address, dates and both borrowers, and the lead moves to the stage your mapping names.
  2. Processing moves the file to a new status in Arive. Your Arive to Leaf360 Mapping moves the Leaf360 loan status and the lead stage to match, without anyone retyping.
  3. A workflow you built on the Loan Status Changed trigger runs: it creates the follow-up task you set, notifies the assigned loan officer, or sends the email template you picked when you built it. What it does is exactly what you configured.
  4. Later you move the file to a status from inside Leaf360. On Direct API, Status Mapping writes that status back to Arive, so the processor sees it there too.
  5. The loan funds as a purchase. The borrower’s lead record updates its address to the new property, and your past-client follow-up starts from the right place.

The workflow in step 3 is the part you design. The workflow builder guide lists the triggers and actions; the Loan Status Changed trigger is one of them.

Limits, stated plainly

  • Writeback from Leaf360 to Arive runs only in Direct API mode, and only for statuses with an entry on the Status Mapping tab.
  • On a Zapier connection, the API Connection Status panel shows Connection Error against Direct API Access. That is expected and needs no fix.
  • A loan that has just funded as a purchase updates the borrower's address to the property they bought; a loan still in progress leaves their stated home address alone.
  • Loans can also arrive by file: the loan importer recognizes Arive's own column headers, so an export straight out of Arive needs no mapping.
  • We do not quote a setup time here. It depends on which mode your company uses and on having the credentials to hand.

Questions loan officers ask

Does the Arive integration sync both ways?

Statuses do, in Direct API mode. Arive to Leaf360 Mapping moves the Leaf360 loan status and the lead stage when a status changes in Arive, and Status Mapping writes a Leaf360 status change back to Arive. Writeback runs only on a Direct API connection, and only for statuses that have an entry on the Status Mapping tab.

I do not see the Arive card on the Integrations shelf.

The card is administrator only. If Arive is not on the shelf at all, you are on a company account, and an administrator at your company has to follow the connection steps and enable it for you.

Loans are not showing up from Arive. What is wrong?

Most often the API keys. Generate them in Arive under User Settings, then API, copy each one and paste it into the matching Leaf360 field, then Test Connection. Also check the LOS Email Alias if your Arive email differs from your Leaf360 login.

A synced loan landed on the wrong status, or the lead did not move.

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.

Can I import Arive loans without connecting the API?

Yes. Export from Arive and upload the file through the loan importer. It recognizes Arive's column headers, including military service status and preferred language for the borrower and co-borrower.

Start free, connect Arive from Settings, and see your own loans in Leaf360. Moving from another CRM? Read the migration checklist first.

Get Started with Arive + Leaf360

Leaf360 connects to the Arive loan origination system by Direct API or Zapier. Loans, borrowers and statuses come across into Leaf360; on Direct API, status changes write back to Arive through the Status Mapping tab.