HubSpot: common errors

This page describes the errors that APIcenter can report for HubSpot, with the cause and the solution. You see the message in the activity of the flow. The messages from APIcenter are in English. Search for the text of the message, which is shown below between quotation marks. The names in the message, such as the name of a deal or property, are different for you.

Is the problem the connection itself, a flow that is not running, or records that are tried again? Then read Connection to an application failed, A flow is not running and Records that fail.

Validation of required fields failed

Message: Validation of required fields failed and Field Validation Failed. The message names the fields that are missing.

Cause: the data of the flow is missing a required field.

• For Send sales orders to HubSpot, dealname is required. This is the order number.
• For Send payments to HubSpot, pipeline, dealstage and dealname are required.

Solution:

1. Open the message and read which fields are missing.
2. Under Data mapping of the flow, check if those fields are mapped.
3. In the source system, check if the order or payment has a value for those fields, such as an order number.
4. Run the flow again.

Pipeline or stage not set

Message: No Pipeline set for Deal!, No Pipeline set for Company!, No Pipeline set for Contact! or No Pipeline Stage set for ....

Cause: the settings of the flow have no pipeline or no stage. Without a pipeline and stage, APIcenter cannot create a deal, company or contact. This applies only to flows that send data to HubSpot.

Solution:

1. Go to the Settings tab of the flow and open the category that is named in the message.
2. For a deal, enter the pipeline in Set the Pipeline to update the deal towards and the stage in Set the dealstage to update the deal towards.
3. For a company or contact, enter the pipeline and the lifecycle stage. See Send customers to HubSpot. If you process only contacts, turn on Only process contact information. Then the pipeline for companies is not needed.
4. Use the name or the ID of the pipeline and the stage, exactly as they are in HubSpot.

Pipeline not found

Message: Pipeline set for deal not found!. The word deal can also be company or contact.

Cause: APIcenter looks in HubSpot for a pipeline with the name or ID from the setting and does not find it. Uppercase and lowercase letters do not matter. A spelling mistake, or a pipeline that you renamed or deleted, gives the same message.

Solution:

1. In HubSpot, check the name and the ID of the pipeline.
2. Change the pipeline setting in the flow so that it matches exactly.
3. Is the pipeline setting optional and do you not need it? Then make the setting empty.

Stage not found

Message: Stage '...' not found in pipeline!.

Cause: the stage from the setting does not exist in the pipeline that APIcenter uses. Often the stage belongs to another pipeline.

Solution:

1. In HubSpot, check if the stage exists in the pipeline from the setting. You can use the name or the ID.
2. Change the stage or the pipeline in the settings so that they belong together.

Stage is in more than one pipeline

Message: Stage '...' found in multiple pipelines!.

Cause: you filled in a stage but no pipeline, and the stage exists in more than one pipeline. Then APIcenter does not know which pipeline to use.

Solution: also fill in the pipeline, or choose a stage that exists in only one pipeline.

Deal already exists

Message: The deal with deal name: '...' was found!.

Cause: for Send sales orders to HubSpot, a deal with the same order number as its name already exists in the pipeline. APIcenter then does not create the deal again. This happens if Update order is off. It also happens if Update order is on and the existing deal is already in the deal stage that is set.

Solution:

• Was the order sent before? Then you do not need to do anything. The deal is already in HubSpot.
• Do you want APIcenter to update an existing deal? Turn on Update order and check the deal stage. APIcenter updates the deal only if the stage in HubSpot is different from the stage that is set.
• Do two orders from different sources have the same number? Make the deal names unique with a prefix or suffix. See Send sales orders to HubSpot.

Deal or invoice not found for a payment

Message: Deal '...' cannot be found! or Invoice '...' cannot be found!.

Cause: Send payments to HubSpot puts payment data on an existing deal or invoice. It does not create one itself. APIcenter does not find the object. A deal is searched by pipeline, deal stage and deal name. An invoice is searched by invoice number. The deal may not exist yet, or the pipeline or stage in the data is not correct. According to HubSpot, it can also take a moment before a new record appears in search results.

Solution:

1. Check if the deal or invoice exists in HubSpot, for example because the order was sent first.
2. Check that pipeline and dealstage in the data are the internal IDs, such as default and closedwon, and not the labels. Also check that the deal is still in that stage.
3. Did you just create the deal? Wait a moment and run the payment again.

Property does not exist

Message: Property: '...' does not exist!.

Cause: a property, option or property group that APIcenter needs does not exist in HubSpot. The name in the message is the name of the property. For an attribute of a product, it is the value that is missing as an option. Examples are the company property for the e-mail address (by default company_email), a property for an attribute of a product, or a property for the main product of variants. The setting Create missing properties in the target system is off. This is the default.

Solution, choose one of the two:

• Create the property yourself in HubSpot. Go to the settings icon, choose Properties and choose the object type. Then click Create property. See Create and edit properties. Check that the name is the same as the name in the message.
• Turn on Create missing properties in the target system, so that APIcenter creates the property itself. Your user in HubSpot then needs the permission Edit property settings.

Option cannot be created

Message: Cannot create attribute option: '...'!.

Cause: the property in HubSpot exists, but the value that APIcenter sends is not yet an option of that property. APIcenter wants to add the option, but this fails because the property does not allow it. According to HubSpot, you cannot change some properties, such as certain default properties.

Solution: add the option yourself to the property in HubSpot, or change the value in the source system or in the data mapping. Then run the flow again. See Create and edit properties.

Company e-mail address is missing

Message: No email field set for company email!, Email field set for company email not found! or Email field set for company email is empty!.

Cause: APIcenter uses the e-mail address of the company to recognize companies and contacts. Something is wrong with the setting Property to use as company email or with the data:

• The setting is empty.
• The property from the setting is not in the data of the order or customer. Then the data mapping does not send the e-mail address to that property.
• The property is present, but it has no value. Then the source system does not send an e-mail address.

Solution:

1. In Property to use as company email, enter the property that holds the e-mail address of the company. The default value is company_email.
2. Under Data mapping, check that the e-mail address of the customer goes to the same property.
3. Does the source system sometimes not send an e-mail address? Then use a default customer with an e-mail address. See Send sales orders to HubSpot.

Association type not found

Message: Failed to find association type!.

Cause: APIcenter links contacts, companies, deals and order lines to each other with an association type. The type from the setting does not exist in HubSpot. Most often there is a typing mistake in the setting, or the value has the wrong form.

Solution:

1. Open the settings of the flow and find the association types, for example contact to company.
2. Write the type in the form that is shown in the setting, for example Contacts-to-Companies: first the object type, then -to-, then the other object type.
3. If you leave the setting empty, APIcenter uses the default type between the two objects.
4. Did you create your own association labels in HubSpot? Then check that the type with that name exists in HubSpot.

Contact cannot be updated

Message: Error trying to update contact for customer: '...'!. After the colon is the e-mail address of the customer.

Cause: HubSpot did not accept the update of the contact. A known cause is the lifecycle stage. According to HubSpot, you can only move it forward. Setting an earlier stage works only if the current value is empty first. Another cause is a value that HubSpot does not accept for a property.

Solution:

1. Open the message and read what HubSpot reports back.
2. Is it about the lifecycle stage? Set the stage back in HubSpot yourself first, or stop APIcenter from updating the pipeline and stage of existing contacts with Update pipeline & stage on existing contacts.
3. Under Data mapping, check that the values you send, such as an option or a country name, exist in HubSpot.
4. Run the flow again.

HubSpot reports too many requests

Message: an error message from HubSpot about a limit, or the HTTP status 429.

Cause: APIcenter sends more requests in a short time than HubSpot allows. HubSpot limits the number of requests per 10 seconds and per day. A stricter limit applies to searching. The limits depend on your HubSpot subscription and on how the app is installed. After that, HubSpot gives the error message for all following requests. The daily limit is reset at midnight (in your time zone).

Solution:

1. For flows that get data, lower the number of records per run with Amount to process.
2. Do more flows or other apps run at the same time on the same HubSpot account? Then spread them over the day.
3. Wait until the limit is over. After that, APIcenter tries failed records again. See Records that fail.
4. Does the message keep coming back? In HubSpot, look at the use of the API. See API usage guidelines and limits.

No access or missing permissions

Message: an error message from HubSpot about access or permissions, or the HTTP status 401 or 403.

Cause: the authorization has expired or was withdrawn, or the access that you gave to APIcenter is missing a permission that the flow needs. According to HubSpot, a message about integration permissions often means that the permission Edit property settings is missing.

Solution:

1. Test the connection and authorize again if needed. See Connection to an application failed and Connect HubSpot to APIcenter.
2. Ask a Super Admin in HubSpot to approve the access, or to change the permissions of the user. See Resolve an integration permissions error.

More information from HubSpot

• API usage guidelines and limits
• Create and edit properties
• Resolve an integration permissions error