If you use the HubSpot integration, understanding when a sync fails is important. Luckily we have an Event Log in our integration where you can spot errors as they happen. 

In this article, we'll cover: 

• What to look for to prevent HubSpot errors from happening
• Common HubSpot errors and how to resolve them

The HubSpot integration is available on the Drift Pro plan and above. 

What to Look Out For

Allowed Options: Many HubSpot errors are most commonly related to values being misaligned between Drift and HubSpot. If the value you are mapping in Drift does not match the value in your HubSpot picklist, this will likely trigger an Invalid Option error. When mapping values to HubSpot picklists, Drift will look for whether the API value matches the Internal Value in HubSpot, so it's very important to check that these match at a 1:1. 

HubSpot Lifecycle Stage: If you use HubSpot, you may be familiar with Lifecycle Stages. While they're a great feature in HubSpot, they can also be a culprit for errors in Drift. You'll often see these errors occur when the values we send from Drift are not being mapped appropriately to the given Lifecycle Stage in HubSpot. Many Lifecycle Stage errors will trigger an INVALID_OPTION message. These can be resolved by matching the correct Lifecycle Stage value to the correct attribute found in Drift, so that they are matched accordingly.

Please note: lifecycle stages are only meant to progress forward, down the funnel. Imports, workflows, and form fields can only set the default Lifecycle Stage property for contacts and companies to a lifecycle stage down the funnel. You can only set a lifecycle stage backwards manually, or in a workflow by clearing the Lifecycle stage property prior to setting the new value.

Common Errors 

Before we dive in, it's helpful to understand the makeup of an error. HubSpot errors are comprised of two parts: the code and the message. 

 Anatomy of an Error: 

 "Code": the number indicating the type of error we're hitting 
"Message":  the context we provide that explains the error

 Now, let's get into the nitty gritty! Below you can find common errors that occur between HubSpot and Drift:  

INVALID_OPTION

Meaning:  There's two things here worth looking at: 1.) Dogs was not one of the allowed options, and 2.) [label:\"cats\"\invalue:\"cats\".

The first part of the message is referring to the value Drift sends to HubSpot when attempting to map the attribute. The second part of the message is the value that is available from the picklist in HubSpot. 

What Drift sends to HubSpot must match what's available on the picklist. If the API value does not match the Internal value in HubSpot, this error will be triggered. 

Solution(s): If you map an attribute in Drift to an attribute in HubSpot that has a picklist, you will need to map a static value from Drift that matches what is available on the picklist. All in all, you will want to adjust your values in HubSpot so that there is a direct match. 

READ_ONLY_VALUE

Error: Failed to update HubSpot contact. Email: email@website.com. Network Error: {"validationResults":[{"isValid":false,"message":"\"ATTRIBUTE\" is a read only property; its value cannot be set.","error":"READ_ONLY_VALUE","name"ATTRIBUTE"},

Meaning: The attribute in question can’t be mapped to as it is read only.

Solution(s): To resolve this, you will want to create another attribute to map to or create a new attribute in HubSpot. 

DUPLICATE_PROPERTY_TO_SAVE

Error: {"isValid":false,"message":"duplicate property value","error":"DUPLICATE_PROPERTY_TO_SAVE","name":"ATTRIBUTE"}],"status":"error","message":"Property values were not valid","correlationId":"cdff6177-bef1-4507-8727-08baea847c1e","requestId":"1f3cf729e9e0ec0ff18e573525dd4fd3"}

Meaning: There are two Drift Attributes being mapped to the same HubSpot attribute.

Solution(s): To resolve this, you will want to adjust your attributes in Drift so that the two attributes are being mapped to different attributes in HubSpot. 

RATE_LIMIT

Error: Failed to create the timeline event of type Conversation closed with end user: xxxxxxx@xxxxx.com. Network Error: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"59ebdc16-d28a-4b61-abb6-1b229a6c2e33","policyName":"SECONDLY","groupName":"publicapi:oauth-secondly:31318:1973303","requestId":"5c50f2bb1294fa3fd1d24a83191c7942"}

Meaning: HubSpot has an API limit, so if too many events are sent at once you’ll see this error. This will often happen if you’re bulk closing conversations.

Solution(s): To fix this, you will want to go back to the conversation that was started with the contact and re-open and re-close the chat. From there, you can check your HubSpot Events Log to check that information synced.