Skip to main content

Hi All,

I am kind of novice here and I am looking some advices and eventually some real help as well.

So, I do have the connection for Salesforce and Arrive (LOS) as well.

I would like to achieve the following:

If a have a new Loan created in Salesforce then search in Arrive based on the Borrower’s phone number in Arrive.

  • If a Loan already there in Arrive with the same phone number, then update the Salesforce-Loan object (Arrive Link ID: … - this can be anything) with the Arrive- Loan ID for future references.
  • If there is no such Loan exists in Arrive, then create one new Loan in Arrive and again update the Salesforce-Loan object (Arrive Link ID: … - this can be anything) with the newly created Arrive- Loan ID.

Any help and comment is welcome and I think for any mid level or pro this would be a piece of cake. If I have this, then I can figure it out the rest by myself, since we do not need to do anything super complicated.

Thank you,

Charles

Hi ​@Paladinka77,

The first part should be fairly straightforward. I’m assuming that your company has Loans set up as a Custom Object in Salesforce, since, as far as I’m aware, Loans isn’t a standard object. If that’s the case, you should be able to create a Zap trigger for New Record created, specific to that object type:

The second part is a bit trickier, since it appears that ARIVE’s Zapier integration is private, meaning that only existing customers have access to it, and so I can’t currently view the documentation. But I think that, most likely, there should be a search action you can use to try to identify an existing record based on a phone number lookup, and then add a Path step to take different actions depending on whether an existing ARIVE record is found:

  • If found: Copy the ARIVE Loan ID or Link to some custom field on the Salesforce Loan object
  • If not found: Create the ARIVE Loan record and then save the details on the Salesforce Loan object

Depending on how ARIVE’s Zapier integration is written, you may actually not need the Path step, because many integrations’s search actions provide a “create record if not found” option, so you can do the find or create in a single pass. 

Hope this helps!


Hey there ​@Paladinka77 👋

Did DennisWF’s reply help to point you in the right direction here?

Let us know if you still need any help at all, want to make sure this gets sorted! 🙂