Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hello Community- I’m looking for some guidance.  I have a customer that is connecting their CRM to QBO.  The issue is that the name of the account in their CRM is often different than the name in QBO.  For example in CRM it would be XYZ Company- R&D Division and in QBO it would be XYZ Company.  Typically the name in QBO is the formal name for billing.  They also have several entries for the same company which will not allow me to link accounts based on their domain.  For existing accounts I could use a lookup table for CRM Account number and QBO Account number but that is going to use a lot of zaps.  Also how would link new customers and how would that table get updated?

 

It seems like this would be a common issue so there must a gracdfule way to do this.  What is the best way for me to link accouts without using account names or domains?  Thank you!

@sboyd 
In the example you gave, you could use a formatter step to split the name “ For example in CRM it would be XYZ Company- R&D Division and in QBO it would be XYZ Company. “ splitting by the “-” and searching what proceeds the “-”. Consistent naming conventions in the CRM could allow this to work across the board. If sometimes they put XYZ Company- R&D but sometimes they put ABC: R&D then issues will be present. 

It is also possible to develop custom integrations that can hit on soft matches but that would only be recommended if there was also a second parameter to match by. 

It may also be possible to set up custom fields to reference to (i.e QBO it in CRM and CRM ID in QBO) but that would likely require some customization as well. All in all, the solution will vary based off of the conventions being used but when at all possible, if trying to set up syncs, it is best to have concrete matches.  

Terms & Conditions