Its been a common and age-old problem with those of us who use integrations regularly that Hubspot's native API property for Emails doesn't like to work well with other systems. Inside Hubspot its a seemless tool, but when linking to other systems like Practifi whic store emails in separate properties for different uses, it can cause quite a problem. For example: - A contact is created under their primary email, but somewhere along the way another secondary or even terciary email is added. All of these emails are stored under one property as a comma separated value. When syncing with another system, that does not use this methodoligy, the other program will only recognize the primary email. This can become a problem when a contact has entered an alternative email in prospecting, service communication, collections, etc. as the users in the other program will not have access to those alternate emails. Inside Hubspot, the workflow parameters don't allow for these additional emails to easily be copied to other fields to fix this problem. This leads to manual work on the end of both programs in the end. Some solutions might include: UI that allows the admin to copy additional email fields to other properties, added functionality that creates rules when additional emails are added to map them to other properties in other programs. For example: - A user is setting up an integration to Salesforce. Within the rules section of the integration, a rule is listed that states 'sync additional emails to x field'
...read more