Sync Salesloft Accounts to HubSpot Companies
This is a 'Workflow' template which means that it is a single standalone workflow.
Some workflow templates can be modified to work with other workflow templates - e.g. to convert a data sync between two services from uni-directional to bi-directional
OverviewCopy
This workflow is a live sync between Salesloft and HubSpot Accounts. It is triggered by any changes occurring in Salesloft, which are then synced to HubSpot.
It is set up to prevent duplicate notifications syncing in HubSpot and can be used for bi-directional syncing. It is designed to work in tandem with Sync Companies Unidirectional HubSpot > Salesloft template or as a stand-alone unidirectional workflow.
Connectors UsedCopy
The following connectors are used in this template. This is provided for reference only - there is no need to read through the linked connector pages, as all you need to know for this template is explained here:
End ResultCopy
The image below shows a synced company in Salesloft and HubSpot:
PrerequisitesCopy
This workflow assumes the following:
You have API credentials set up with Salesloft and HubSpot.
Getting LiveCopy
In order to configure this workflow for use, simply:
Workflow logicCopy
The overall logic of the workflow is:
The trigger waits for Salesloft to notify Tray of company creation or update.
Using 'Domain' determines whether a matching company for the Salesloft account is available in HubSpot.
If yes, using Company ID Tray collects personal information on that company from HubSpot.
If not, then a new company is created in HubSpot.
Once a company match has been found; the workflow compares Salesloft account's and HubSpot company's payload.
If there is any difference in payload, then the information for the company in HubSpot is updated.
If there is no difference in payload, then the workflow terminates.
Implementation notesCopy
Build and compare HS and SL payloadCopy
Before updating the data in HubSpot the workflow compares the new data received through Salesloft with the existing data from HubSpot.
If there is no difference between them, the workflow ends without performing any action. If a difference is found, the workflow updates the new information in HubSpot.
To do so, the workflow creates Salesloft and HubSpot payload by:
Choosing the fields they wish to be part of the payloads. Refer to Choose fields in the Getting live section.
Build Sl/HS Payload step: creates separate objects of key/value pairs for HubSpot and Salesloft fields using the Add key/value pairs operation.
This operation adds key/value pairs from the array list to a source object as properties and then returns a single object.
Compare Payload to Payload: These objects will be then compared using the Equals operation.
The operation returns true if both the objects are the same, false otherwise.